Description of problem:
The log file /var/log/bittorrent/btseed.log remains empty, althought btseed is seeding
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Put a file and its torrent in /srv/bittorrent/data
2. service btseed start
3. [ruben@odin ~]$ ls -l /var/log/bittorrent/btseed.log
-rw-r--r-- 1 root root 0 2007-06-11 23:22 /var/log/bittorrent/btseed.log
The same output I get when I start btseed by hand:
[ruben@odin ~]$ btseed /srv/bittorrent/data/ >> ~/btseed.log 2>&1 &
[ruben@odin ~]$ ls -l btseed.log
-rw-rw-r-- 1 ruben ruben 450559 2007-06-11 23:44 btseed.log
Maybe this has something to do with the fact that its running under runuser?
How long is btseed running before you decide it's not logging? The output to the
log file is buffered and can take quite a while for anything to get written to disk.
Try changing the display_interval option for SEEDOPTS in
/etc/sysconfig/bittorrent to a smaller number (like 5) to increase the log
volume and something should get written to the disk more quickly.
Strange, I waited at least half an hour or so.
But now it's logging (--display_interval = 5) data.
Thanks for your help!
I recall seeing the same issue when I was initially testing the initscripts; at
a log message every 5 minutes, it can take quite a long time before enough data
has accrued to be worth writing to disk.