delorie.com/archives/browse.cgi | search |
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: | <E087F7025D7E494B8015119695CEDB4C0209B0C2@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: | RE: kill(pid, 0) issue |
Date: | Thu, 18 Dec 2003 16:58:51 +0100 |
MIME-Version: | 1.0 |
Yes you are right I somehow missed the sentence: >>kill(pid, 0) will succeed on both linux and >>cygwin if the process is not reaped by calling wait (or waitpid, etc.) >>first. Thanks, Maciek -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |