Re: killing a large lists of pids
- From: "Kurt M. Weber" <kmw@xxxxxxxxxx>
- Date: Thu, 29 Nov 2007 16:53:19 -0600
J de Boyne Pollard wrote:
JS> Guess the reason is that typically the parent processes have
JS> lower PIDs and killing parents may take the children along
But, conversely, killing the children first would often tend to cause
the parents to exit of their own accord, if (for example) the parents
were shells executing a command pipeline.
Both of these are superficially attractive rationales. But they both
break down. In reality, process IDs are not guaranteed to be created
in _any_ order.
To add to that...even if you know that the particular system this will be
done on does indeed allocate PIDs sequentially, it still breaks down when
the maximum PID value is reached and they roll back over.
Kurt M. Weber
- Prev by Date: Re: Design of x-window system
- Next by Date: Re: High-performance server: epoll or a thread pool?
- Previous by thread: Re: killing a large lists of pids
- Next by thread: Re: killing a large lists of pids