> Once a process in in the 'Z' state it should not receive any
> signals. Its signal handlers are already gone. It's just a
> snippit of sys_exit code that remains. If the process truly
> is in the 'Z' state, its input/output/error file-descriptors
> should have already been closed so the time-out from the
> shutdown should have already happened.
Hi Dick,
You are right, its not a zombie.
The process is held up in "drain" in the tty close of the
processes stdin (/dev/ttyS0).
(I assumed brackets in ps -ef meant zombies, but that's wrong)
I added some code to make a short timeout in the "tty close" part of
the driver, then check the values of:
current->signal->shared_pending.list.next
current->signal->shared_pending.list.prev
They *do* change, when I send the process (date) a signal.
The kernel just isn't waking up the driver's "wait" to let it
know that there are signals pending.
Also, why did this work under 2.4?
This is why I was wondering if this was intentional, or was just an
oversight...
Thanks!
Scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
