I have done some test and this consitantlay doesn't work but the debug flow is consistantly differnet.
Sometime both lines are printed:
[<time>] [<file_name>--<tracker_domain>:80] appended event "stopped"; announcing in 0 seconds (announcer.c:971)
[<time>] [<file_name>--<tracker_domain>:80 ...
Search found 4 matches
- Wed May 19, 2010 4:31 pm
- Forum: General
- Topic: Headless Transmission 1.93 - Doesn't send event=stopped
- Replies: 4
- Views: 2872
- Wed May 19, 2010 3:33 pm
- Forum: General
- Topic: Headless Transmission 1.93 - Doesn't send event=stopped
- Replies: 4
- Views: 2872
Re: Headless Transmission 1.93 - Doesn't send event=stopped
I am running it headless BTW.
- Wed May 19, 2010 3:30 pm
- Forum: General
- Topic: Headless Transmission 1.93 - Doesn't send event=stopped
- Replies: 4
- Views: 2872
Re: Headless Transmission 1.93 - Doesn't send event=stopped
Apologies.
I meant to mention in my initial post that I already have this environment var set.
This is how come I have the debug.
I meant to mention in my initial post that I already have this environment var set.
This is how come I have the debug.
- Wed May 19, 2010 3:18 pm
- Forum: General
- Topic: Headless Transmission 1.93 - Doesn't send event=stopped
- Replies: 4
- Views: 2872
Headless Transmission 1.93 - Doesn't send event=stopped
I have recently built from source Transmission 1.93 for Centos and have an issue when closing.
When transmission-daemon starts it sends announces to my tracker with event=started. This is great. My tracker logs the client as a peer and starts downloading/seeding.
I then kill the process (either ...
When transmission-daemon starts it sends announces to my tracker with event=started. This is great. My tracker logs the client as a peer and starts downloading/seeding.
I then kill the process (either ...