|
Home > Archive > Unix Shell > November 2007 > fcitx zombie process
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
fcitx zombie process
|
|
|
| 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.
| |
| Barry Margolin 2007-11-23, 7:20 pm |
| In article
<f72f1b68-e7ca-4c66-a962-873ff6f4e765@d27g2000prf.googlegroups.com>,
david <david19842003@gmail.com> wrote:
> 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 ***
| |
| Kenny McCormack 2007-11-23, 7:20 pm |
| In article <barmar-443D86.16054023112007@comcast.dca.giganews.com>,
Barry Margolin <barmar@alum.mit.edu> wrote:
>In article
><f72f1b68-e7ca-4c66-a962-873ff6f4e765@d27g2000prf.googlegroups.com>,
> david <david19842003@gmail.com> wrote:
>
>
>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
|
|
|
|
|