On Thu, 31 Jan 2002, Jim Jagielski wrote: | I was refering to the situation where the kids don't auto-suicide | upon being orphaned. If they don't, the picking them off is tough | out-of-process. | | It's looking like we need a decision vote: | If the parent process dies, should the remaining child processes | "gracefully" self-terminate.
>From a users' standpoint, it would seem more like a bug in apache if s/he tries to shut apache down via apachectl, and then start it back up. First, the shutdown will fail, because the ppid is no-longer existing (and thus producding the "unclean shutdown message), and when the attempt by the bewildered admin is made to start apache again, it fails because the childs are still bound to ports and whatnot. Although I hold no voting power here, I'd say that the children are to die with the parent. That, or apachectl is changed to kill all children if $1='stop' and the parent is no-where to be found. Either way, things need to stay consistent from an admin POV... with the propper warnings and complaints being displayed/logged, of course. /dale
