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

List:       kde-core-devel
Subject:    Re: Session Management Server README
From:       Matthias Ettrich <ettrich () trolltech ! com>
Date:       2000-04-10 11:51:11
[Download RAW message or body]

Am Son, 09 Apr 2000 schrieb David Faure:
> Bug report:
> 
>   797 ?        Z      0:00 [kwelcome <defunct>]
>   803 ?        Z      0:00 [dcopserver <defunct>]
>   804 ?        Z      0:00 [ksmserver <defunct>]
>   806 ?        Z      0:00 [kded <defunct>]
>   807 ?        Z      0:00 [kicker <defunct>]
>   808 ?        Z      0:00 [kdesktop <defunct>]
>   809 ?        Z      0:00 [kio_uiserver <defunct>]
>   810 ?        Z      0:00 [kcookiejar <defunct>]
>   814 ?        Z      0:00 [konsole <defunct>]   
> 
> pstree shows all those processes to be children of ksmserver.
> Unless I'm wrong, they are all KUniqueApplication, i.e. they fork
> on startup. I guess the fix would be a SIGCHLD handler in ksmserver ?

Yes. 

But I wonder how kwelcome, dcopserver, kded, kicker, kdesktop could become
children of ksmserver. According to startkde they are launched _before_
ksmserver. But it's certainly true for konsole.

Matthias

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