This is the mail archive of the
mailing list for the cygwin project.
RE: /bin/kill -f WINPID; for a rogue cygwin process?
On 11 December 2007 19:45, Tom Rodman wrote:
> The fact that the process vanished was interesting, but my main question
> is why did 'kill' want to open pid 6340?
Couple of data points:
a) Windows PID != Cygwin PID. (Although they are generally the same, it isn't
b) Cygwin sometimes keeps a dummy cygwin PID and process details hanging around
after the real win32 process has died; for example, if a parent process is going
to wait4() on the defunct child.
Can't think of a witty .sigline today....