Its obvious that bitornado (and I would guess bittorrent, because they share the same code-base) does not have signal handling support. I typically use control-c or 'q' to quit a torrent and avoid sending unnecessary signals to any program unless I know what they do ahead of time.
Killing a process with inappropriate signals that it isn't written to handle will cause data loss, no matter what program it is. I will not classify this bug as grave because of this reason. In fact, this is a wishlist bug, you want bittorrent to have some graceful quit functionality on a kill signal, which it does not have. I will forward this request to the upstream for their consideration. In the meantime, I would suggest doing what most everyone else I know does who wants to detach from a torrent and then re-attach and change things at a later time -- install and run the screen program before launching btdownloadcurses or btlaunchmanycurses and then detach from the screen session. You can resume the screen session at a later time without problems, and execute a proper quit to the program. micah Jeff Bonham schrieb am Monday, den 17. January 2005: > I just tested a btdownloadgui.bittornado process 15 times with signals 1 > through 15. With each signal (except 13, which does not kill the > process) the ratios were reset to zero on the next startup, the file was > rescanned and a connection to the tracker was left hanging. > > This bug also should be set to severity "grave" since it causes data loss. > > -- > Jeff Bonham > [EMAIL PROTECTED] > PGP Public Key ID: BA289747 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
