--logfile doesn't appear to work on Solaris 10

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
oh_noes
Posts: 15
Joined: Wed Dec 08, 2010 9:02 am

--logfile doesn't appear to work on Solaris 10

Post by oh_noes »

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?

Code: Select all

$ rm "/data/log/transmission-daemon.log"
$ touch "/data/log/transmission-daemon.log"
$ /usr/local/transmission/bin/transmission-daemon --config-dir /data/info --logfile "/data/log/transmission-daemon.log" --no-portmap --no-lpd 
$ pgrep trans
13910
$ sleep 60
$ tail -5 "/data/log/transmission-daemon.log"
$ 
oh_noes
Posts: 15
Joined: Wed Dec 08, 2010 9:02 am

Re: --logfile doesn't appear to work on Solaris 10

Post by oh_noes »

I should also note that:

Code: Select all

/usr/local/transmission/bin/transmission-daemon --config-dir /data/info --log-debug --foreground
Runs and logs everything to stdout without a problem. But passing in --logfile doesn't appear to reliably work for me.
gunzip
Posts: 272
Joined: Wed May 05, 2010 2:12 am

Re: --logfile doesn't appear to work on Solaris 10

Post by gunzip »

what to you have entered in settings.json for

"message-level": ?,

also verify that the user running transmission-daemon has valid permission to write at /data/log/transmission-daemon.log

otherwise everything looks right and it may be a Solaris-specific bug. I do something very similar in Linux and it all works fine.
oh_noes
Posts: 15
Joined: Wed Dec 08, 2010 9:02 am

Re: --logfile doesn't appear to work on Solaris 10

Post by oh_noes »

Hi gunzip,

My message-level is 3.

Code: Select all

    "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 I needed to be aware of.
Post Reply