Zombie accounting processes

[George-Cristian Bîrzan]

On Mon, 2006-02-13 at 14:36 +0000, Phil Mayers wrote:
> > It's a Slackware 10.1 (I think, could be 10) with a 2.6.14.3 kernel.
> > Same happened with 2.4.29 and 2.6.12.
> 
> Ok, so the FreeRadius executable should have only one PID since it's 
> running the new threading, unless you've got an old libc?

Hm. 2.3.4, not that old, but:

root at radius:~# ps u $(pgrep radiusd)
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root      5258  0.0  0.2 16908 2140 ?        Ss   18:47   0:00 radiusd
root      5259  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5260  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5261  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5262  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5263  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5264  0.0  0.2 16908 2140 ?        S    18:47   0:00 radiusd
root      5978  0.0  0.2 16908 2140 ?        S    18:57   0:00 radiusd

> >> Hmm. What does "ps -ejf" (on Linux - translate for closest
> equivalent on 
> >> other systems) say for these?
> > 
> > root     25065 24736 23880 23880  0 15:11 ?        00:00:00
> [acct-ng.pl] <defunct>
> > root     25073 23885 23880 23880  0 15:11 ?        00:00:00
> [acct-ng.pl] <defunct>
> > 
> 
> ...so why do these have different parent PIDs (2nd column)? Could 
> "acct-ng.pl" be itself forking? What process are those PIDs? 

radiusds.

Also, as a sidenote, I've tried with an empty bash script, same thing
happens, it gets stuck as a zombie when called for accounting stop.

-- 
George-Cristian Bîrzan
Network Engineer
_______________________________________
RCS & RDS Constanta
Tel.: +40341.400.401 / +40341.400.402
Fax: +40341.400.450
http://www.rcs-rds.ro
_______________________________________

Privileged/Confidential Information may be contained in this message. If
you are not the addressee indicated in this message (or responsible for
delivery of the message to such person), you may not copy or deliver
this message to anyone. In such a case, you should destroy this message
and kindly notify the sender by reply e-mail.