Bug 243788 - btseed doesn't log output
Summary: btseed doesn't log output
Alias: None
Product: Fedora
Classification: Fedora
Component: bittorrent   
(Show other bugs)
Version: 7
Hardware: All Linux
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-06-11 21:45 UTC by Ruben Kerkhof
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-12 09:12:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ruben Kerkhof 2007-06-11 21:45:12 UTC
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

Expected results:

The same output I get when I start btseed by hand:

[ruben@odin ~]$ btseed  /srv/bittorrent/data/ >> ~/btseed.log 2>&1 &
[2] 28769
[ruben@odin ~]$ ls -l btseed.log 
-rw-rw-r-- 1 ruben ruben 450559 2007-06-11 23:44 btseed.log

Additional info:

Maybe this has something to do with the fact that its running under runuser?

Comment 1 Paul Howarth 2007-06-12 06:52:31 UTC
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.

Comment 2 Ruben Kerkhof 2007-06-12 08:49:03 UTC
Strange, I waited at least half an hour or so.
But now it's logging (--display_interval = 5) data. 

Thanks for your help!

Comment 3 Paul Howarth 2007-06-12 09:12:24 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.