Transmission

Hrmm, how can I report it to the pkg-config maintainers? No pkg-config binaries exists on the system at all. From a user point of view, having that variable declared (LIBCURL_CFLAGS
and LIBCURL_LIBS) should bypass any call to pkg-config?

Found the fixed.

Even though I was declaring the environment vars, it still wanted pkg-config.
And it passes the 'check' and uses the env vars as expected.

Clean Solaris 11 install.


$ wget curl-7.21.6.tar.gz
$ ./configure --prefix=/usr/local/curl
$ make
$ sudo make install
$ wget libevent-2.0.11-stable.tar.gz
$ ./configure --prefix=/usr/local/libevent
$ make
$ sudo make install
$ wget transmission-2.22.tar
$ CFLAGS="-L/usr/local/libevent/lib -R/usr ...

Hi gunzip,

My message-level is 3.

"message-level": 3,

According to EditConfigFiles 3 is debug, so I would expect everything to be constantly logged. it definitely has full write access to the directory and that file.

I will log a bug, thanks; I just wanted to check there wasn't a 'quick' that ...

What version?

I had a tonne of problems on 2.13 with it crashing and RPC dropping out etc.

So far upgrading to 2.13+ (latest trunk) seems to have fixed all my problems.

I should also note that:
Runs and logs everything to stdout without a problem. But passing in --logfile doesn't appear to reliably work for me.

This one is an interesting one. For 99% of the time, logfile does nothing and nothing is written to it. Sometimes, randomly it will write to the file and then stops halfway through the line.

Anyone seen this before? Is my parameter order wrong?



$ rm "/data/log/transmission-daemon.log"
$ touch ...

I'm writing a Solaris SMF script to manage transmission-daemon.

What's the correct and supported way to stop transmission-daemon *cleanly*?

I've seen an example, and it only had kill -9 which isn't very nice. The Linux script uses start-stop-daemon which doesn't tell me the actual command it sends ...

Turns out this is because I wasn't allow Ubuntu's TCP/6969 tracker port out my firewall. Once I allowed TCP/6969 - transmission-daemon immediately crashed.

It allowed me to add more information to my current bug report though, which is good news.

https://trac.transmissionbt.com/ticket/3812

I've finally been able to get transmission-daemon running on Solaris 10 x86 without it crashing with a Segmentation Fault. I achieved this by manually compiling libevent-1.4.14b.

Now to my hopefully final problem! transmission-daemon is running without a problem. BUT it doesn't actually do anything ...

Thanks. Your post was exactly what pointed me in the right direction.

My version was 1.4.13, which had THIS BUG. Upgrading to 1.4.14b fixed this problem.

I still wish I could run transmission-daemon 2.13 on my Solaris 10 U9 x86 server without getting a segfault :/

Cheers

Hi Transmission BT team,

I have compiled and install Transmission-Daemon on Solaris 10 U9. Now when I run it, I get the following debug output to stdout:


(I get 5-10 of these every second)

$ /usr/local/transmission/bin/transmission-daemon --config-dir /export/home/transmission/info --log-debug ...

Thanks. I managed to instal 2.12 by changing meta*.c strsep() to strtok().

Thanks for fixing this bug in 2.13.

I've run into a similar problem with Solaris 10 U9 x86 using Transmission 2.12.


Full details here: https://trac.transmissionbt.com/ticket/3812

I'm trying to get Transmission 2.12 (Daemon) installed on Solaris 10 Update 9 x86.

I'm using GCC make and a bunch of packages from SUNFreeware. I'm making progress, but I'm stuck on the following.


$ cd transmission-2.12

$ export LIBCURL_CFLAGS="-I/usr/local/include"
$ export LIBCURL_LIBS="-L ...