[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 64785] ksmserver fails to quit when session ended
From:       grant mcdorman <grant.mcdorman () cedara ! com>
Date:       2003-11-20 15:43:11
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=64785     




------- Additional Comments From grant.mcdorman@cedara.com  2003-11-20 16:43 -------
> > Commenting out the line allows ksmserver to exit normally.
> >
> something else probably breaks instead. :}

It's to prevent accumulation of zombie ("defunct") processes, and serves no
other function. This will only happen if ksmserver executes processes without
using KProcessController and does not explictly wait for the PID; a quick grep
of the code didn't show any such case. In addition, at the moment on my Solaris
8 system with 3.1.4, there are no zombie processes.

> > Presumably on some systems (Linux, perhaps?) signal() and sigaction() are
> > independant.
> >
> i don't think that's possible. it must have different reasons that it works on > most other systems. 

Perhaps. However, I can't see how it would work otherwise - KProcessController
will only indicate the process finished if it receives a SIGCHILD. I'm not going
to worry about it, though <grin>.
[prev in list] [next in list] [prev in thread] [next in thread]