Actually, it's not pine per se that's killing the children, but the fact that they're in the same session with pine as the session leader.
If I just fire up pine in a pre-existing xterm then get it to open up an attachment, then close pine, the viewing program remains open. If I run 'xterm -e pine', then all the processes have pine (or 'sh -c pine', actually) as the sessionleader, so both xterm and the kernel come along and send SIGHUPS to all the children including the MIME viewer when the tty is closed. The viewer is already forked off in a 'sh -c' process that runs the process in the background and removes the temporary file after the process exits. If after the fork, before execing 'sh -c', pine called setpgrp, I imagine this problem would go away. Since the viewer is not likely using the tty (say, it's xpdf displaying a GUI), then sending it a SIGHUP is non-sensical, and so it makes sense to put it as its own session leader. -- TimC Actually, I was most impressed when I looked up into the London sky and saw a star through all the light pollution. A few of us checked a few astronomy references to try and identify it, and we're reasonably confident that it was Sol. -- Peter Corlett in ASR -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
