Anoop - I like your script, basically I came up with some sort of script like this, which basically let me know the cmdline and then process. However, 32000 is an enormous number and to analyze them is literally the scariest duty of a system admin.
Wish all the developers in this world wrote good code. !! On Mon, Feb 4, 2013 at 2:47 PM, Tavish Naruka <tavishnar...@gmail.com>wrote: > > > > On Sat, Feb 2, 2013 at 8:49 PM, Amar Akshat <amar.aks...@gmail.com> wrote: > >> Hi, >> >> Other day I was writing a small pro-active system monitoring script in >> Ruby, and I forgot to close my IO pipe for pgrep command, every time I >> checked my system status. >> So after a day, there were more than 32,000 zombie pgrep processes. I >> could >> only run bash commands and nothing else. >> > > > kill is a bash builtin, so you can kill a process whose pid you could get > from /proc/ bash completion and issue a killall immediately after it and > hope that a fork works. maybe try a few times. > > -- > Regards > Tavish Naruka > -- Thank you... *Amar Akshat (アマール)* *"Walking on water and developing software from a specification are easy if both are frozen."* _______________________________________________ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
