hi yall. lovin daemon but there seems to be a problem with the new feature to run script on complete...
here is the course of events (to reproduce the issue)...
a torrent completes... daemon triggers the complete-script ... it waits
the script tells daemon to move data to different locations (depending on the torrent's name & some rules)... it waits ... at this point the script is waiting for daemon ... daemon is waiting for the script ...
eventually the script times out (no response from daemon) & daemon starts up again
rather then waiting for the script to complete, shouldn't daemon spawn it as a separate process & continue its business ? this way it can focus on the other torrs (and still respond to the script ). for the record - this is the perl script im using: myTV @hourly via cron
if im missing something, or doing something wrong, please let me know
thanks
~z
zosky wrote:Longinus00, you are a pro! thanks
that a freakin easy work-around.
(kinda feel like a dip for not thinking of it myself)
on-complete calls man-in-the-middle
man-in-the-middle forks & dies
daemon picks up again
myTV tells daemon to move stuff
this should still be considered a bug ?
daemon should do the forking, right
I believe they made the script call blocking so that if you needed to do something to a file that transmission may have open that you could do your thing without transmission changing the files... Thus leaving the option to simply put a control script in that forks and doesn't block..
I think i have the same problem
I'm trying to run transmission-remote from a script.
When i launch it from the command line, everything runs fine
But when it is run from the script-torrent-done-filename directive, i get a timeout (RPC ERROR)
What does "fork a script" mean ?
How am I supposed to do that ?