I'm currently busy with a graphical front-end for smbclient, which allows me to click-and-download files from remote Samba hosts. Downloading is done simply by `back-ticking' a smbclient command.
It is possible to stop ongoing downloads by sending a HUP signal to the current process group (as stated in the PerlIPC manpage). This feature works fine until I spawn my graphical front-end from another Perl script! The kill-signal seems to be ignored and the smbclient program keeps running.
Is there a reliable way to make sure a script can kill all of his children even if the script itself is a child?
Thanks in advance!
-- JaWi
"A chicken is an egg's way of producing more eggs."
In reply to Reliable killing children by JaWi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |