Bug#387658: bittornado: Still affects non-curses btlaunchmany
El jue, 09-11-2006 a las 02:36 +, Cameron Dale escribió: On 11/8/06, Javier Kohen [EMAIL PROTECTED] wrote: Package: bittornado Version: 0.3.15-4 Followup-For: Bug #387658 You might try upgrading to the latest version (0.3.17-1), just to be sure this isn't fixed in the new upstream. This bug seems to be affecting the non-curses version of btlaunchmany (i.e. /usr/bin/btlaunchmany). The only way to exit this application seems to be a SIGTERM, which apparently doesn't let the shutdown call be reached. Your problem is probably stemming from your exiting from btlaunchmany abnormally (i.e. without a SIGINT using Control-C, which is the normal way to exit). Have you tried using a SIGINT/Control-C to exit? If that doesn't work, then this is a separate problem from this bug. You may want to create a new bug report containing information about why you can't use a SIGINT/Control-C to exit. If you're running btlaunchmany in screen though, that could also explain the problem, as there is a definite problem with bittornado and screen (there are already bugs for that). You are absolutely right, I should have been sending it a SIGINT. However, that's not obvious when you're running a headless application on the background. I'll look into adding that information to the manpage, or patching the application to handle SIGTERM gracefully when the latest version hits testing in ‒most likely‒ a couple days. Thanks, -- Javier Kohen [EMAIL PROTECTED] ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] signature.asc Description: Esta parte del mensaje está firmada digitalmente
Bug#387658: bittornado: Still affects non-curses btlaunchmany
Package: bittornado Version: 0.3.15-4 Followup-For: Bug #387658 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This bug seems to be affecting the non-curses version of btlaunchmany (i.e. /usr/bin/btlaunchmany). The only way to exit this application seems to be a SIGTERM, which apparently doesn't let the shutdown call be reached. I don't use the curses version, as the whole point for me of using bittornado is that I can leave it running unattended on a headless server. Unfortunately I'm not versed in Python system programming to the level where I can suggest a solution or supply a patch. Maybe it can trap the signal and start a clean cleanup? - -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18.1-ck1 Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUcrI823633cP2P8RAibBAKCQjjtAPA/pUzVa8aWzRuqYAlmmLQCfVi/r ylKMygf95LYKc3SyYOXOc9U= =ANR/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387658: bittornado: Still affects non-curses btlaunchmany
On 11/8/06, Javier Kohen [EMAIL PROTECTED] wrote: Package: bittornado Version: 0.3.15-4 Followup-For: Bug #387658 You might try upgrading to the latest version (0.3.17-1), just to be sure this isn't fixed in the new upstream. This bug seems to be affecting the non-curses version of btlaunchmany (i.e. /usr/bin/btlaunchmany). The only way to exit this application seems to be a SIGTERM, which apparently doesn't let the shutdown call be reached. Your problem is probably stemming from your exiting from btlaunchmany abnormally (i.e. without a SIGINT using Control-C, which is the normal way to exit). Have you tried using a SIGINT/Control-C to exit? If that doesn't work, then this is a separate problem from this bug. You may want to create a new bug report containing information about why you can't use a SIGINT/Control-C to exit. If you're running btlaunchmany in screen though, that could also explain the problem, as there is a definite problem with bittornado and screen (there are already bugs for that). Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
