Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <E087F7025D7E494B8015119695CEDB4C0209B0BF@zpl02exm01.mpsc.mot.com>
From: Nowakowski Maciej-AMN011 <maciej DOT nowakowski AT motorola DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: kill(pid, 0) issue
Date: Wed, 17 Dec 2003 17:23:20 +0100
MIME-Version: 1.0
Content-Type: text/plain

Hi all,

My application creates additional process using fork() function. Created child process listens on a socket and exits when it receives anything. The main process checks the child PID using kill(pid, 0) with child PID as a parameter. Even when the child has exited this function call returns 0. When I have supplied any PID which hasn't ever existed it's fine and kill(non-existentPID, 0) returns -1.

Has anyone experienced something like this?

I'm using Cygwin 1.5.5 version(DLL version).

Regards,

MacNowak

P.S. For now I'm using kill(pid, SIGCONT) as a workaround.

--
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/