From: Maglinger, Paul (PMAGLINGER@scvl.com)
Date: Tue Mar 11 2003 - 15:37:31 EST
Original message:
Periodically I check the processes running on our Tru64 5.1a PK3 cluster and
it looks like we have sleep processes sitting out there that are child
processes of init, which is a child process of kernal idle. If using a
command such as:
sh -c sleep 60
what could cause it to ever become a child process of kernel idle?
My thanks to Dr. Blinn, Volker Becker, Bryan Lavelle, Rich Copeland, Jay
Vlack, Lars Bro and Steve Dyer, who all basically said that this is normal
system operation typical when a parent process exits without waiting for the
children processes to exit, the orphaned child process is then "inherited"
by init. This can also occur if a parent process is killed, then again the
orphaned child processes will be inherited by init.
As far as telling which processes under init are actually orphaned, it was
suggested that I might "diff" outputs and see which processes are not
accumulating run time.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:10 EDT