Alessandro Vesely writes:
> Currently, the shutdown code just gives up, after a timeout, in this manner. I> do agree that an attempt should be made to kill all processes, after a > reasonable timeout, so it's something that I need to look at.To kill by pid is going to be difficult for forked filters. I issue a callkill(0, SIGTERM) when the pipe is closed, but I had previously called setsid().SIGTERM (15) should suffice to quickly exit; SIGKILL (9) is what I'd call "overkill". It seems several users issue `killall -9 ...`. It shouldn't be needed, and I'd expect some kind of bug report if runaway children refuse to exit, please.
Well, there are various ways to make sure that child processes get SIGKILLed. The traditional way to do this is with process groups.
Probably the best thing to do would be to kill all the processes, but exit with a non-zero exit code.
systemd takes this one step further, and puts all systemd-started processes in a container. On Fedora, a shutdown is going to kill any stuck filter processes, after filterctl stop bails out; so this is a non-issue on Fedora(*).
(*) This is not intended to be an endorsement of systemd.
pgpjtOIx7pw2e.pgp
Description: PGP signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
