[Prev][Next][Index][Thread]

<defunct> LAT-started processes



We recently upgraded from 3.2g to 4.0a on an Alpha 2100.

We have a program that logs people out if they are idle by sending a HUP
signal to the session leader (as reported in utmp).  This worked great
under DU3.2g.  Now, sometimes the processes thus killed are not reaped,
leaving <defunct> processes around and an stale entry in utmp.  The
processes' parent is 1 (init).

Anyone experience anything similar or have any ideas?  Could init be
missing the SIGCHLD signal or something?

John Peterson -- University Networking Services -- Brigham Young University
Internet: John_Peterson@xxxxxxx                       Phone: (801) 378-5007