home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:5013 comp.sys.hp:10304
- Newsgroups: comp.unix.admin,comp.sys.hp,ctp.it
- Path: sparky!uunet!psinntp!fsg!onward
- From: onward@fsg.com (Onward Lam)
- Subject: Re: Unkillable processes
- Message-ID: <1992Sep10.144955.1445@fsg.com>
- Organization: Fusion Systems Group, New York City
- References: <1992Aug26.180629.385@ctp.com> <1992Sep03.212714.28300@quaker.uucp>
- Date: Thu, 10 Sep 1992 14:49:55 GMT
- Lines: 30
-
- In article <1992Sep03.212714.28300@quaker.uucp> raymond@quaker.UUCP (Raymond C. Leung) writes:
- >
- >By the way, I have another type of unkillable processes which are
- >zombies left by some software applications. Use command `ps` I can see
- >they are "<defunc>" and `top` shows the number of zombies on my system.
- >HP people blame the application not handling exit properly.
- >They said their parent process should wait() for their child processes
- >before termination. However, vendor engineer of that software told me
- >that zombie is normal! S o o o, I wouldn't worry about it. :^)
- ^^^^^^^^^^^^^^^^
- >
-
- NO, NO, NO. Zombies are most definitely NOT normal.
- Go tell your software vendor. Agreed that they do NOT affect the operation
- of your application, but they still take up a process slot.
-
- Imagine an application which fork()s every hour and the children exits
- soon after they were created. After 1 day you will have 24 zombies.
- In a week you will have 168. If the application is not owned by root,
- you won't even last that long (more like 2 days and change, assuming
- a 50 process per user limit).
-
- Bottom Line: Get your vendor to fix it.
-
-
- --
- - Onward Lam Internet: onward@fsg.com -
- - Fusion Systems Group Uucp : uupsi!fsg!onward -
- - 225 Broadway, 24th Fl. Voice : +1 212 2858001 -
- - New York, NY 10007 Fax : +1 212 2858705 -
-