When the system started, there was a zombie process called 'fcitx'
which was the child of x-session-manager.
How to deal with it? I know the zombie process is a process that
doesn't have father.
In article
david
> When the system started, there was a zombie process called 'fcitx'
> which was the child of x-session-manager.
> How to deal with it? I know the zombie process is a process that
> doesn't have father.
No, a zombie process a process that DOES have a parent and has
terminated, but the parent hasn't called wait() to get its termination
status. So the problem is that x-session-manager isn't calling wait()
when necessary.
--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***
*** PLEASE don't copy me on replies, I'll read them in the group ***
In article
Barry Margolin
>In article
>
> david
>
>> When the system started, there was a zombie process called 'fcitx'
>> which was the child of x-session-manager.
>> How to deal with it? I know the zombie process is a process that
>> doesn't have father.
>
>No, a zombie process a process that DOES have a parent and has
>terminated, but the parent hasn't called wait() to get its termination
>status. So the problem is that x-session-manager isn't calling wait()
>when necessary.
Or, more to the point, that, either:
1) x-session-manager isn't double-forking to spawn the process.
or 2) x-session-manager isn't ignore SIGCHLD