On 26 April 2006 20:21, Jerry D. Hedden wrote:
> In this case, I used the full 20060426 snapshot and generated some stuck
> processes. The output from 'ps' showed the following:
>
> PID PPID PGID WINPID TTY UID STIME COMMAND
> 2944 1 1332 29292 ? 78809 13:54:03 /usr/bin/diff
> 32184 1 436 2860 ? 78809 14:00:03 /usr/bin/mv
> 1560 1 28372 29084 ? 78809 14:06:05 /usr/bin/diff
> 9768 1 23420 24436 ? 78809 14:12:04 /usr/bin/diff
>
> Looking at the Windows Task Manager, those processes were not listed,
> but what I suppose to be their shell processes were:
>
> Image Name PID
> bash.exe 2736
> bash.exe 9500
> bash.exe 29048
> bash.exe 30324
>
> Note that no bash processes were listed by Cygwin under 'ps'. (Is this
> a clue?)
Um. I wonder if those processes are or aren't actually there.
Isn't there something about bash keeping a pid table of recently-dead
kind-of-zombie processes hanging around for a while? Do they show up in "ps"?
I have a vague memory but haven't tracked down the thread yet. EB or CV might
be able to weigh in on this.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
