X-Spam-Check-By: sourceware.org Date: Thu, 29 Mar 2007 10:50:36 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 'kill' cannot see other process but its own PID ? Message-ID: <20070329085036.GA26240@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 29 09:30, Jurgen Defurne wrote: > Hello, > > I just discovered that 'kill' is not able to test (-0) for processes > which have been started from the cygwin environment, but > running as another user, in this case as a service (UID = 0). > > Is this a problem stemming from the cygwin environment > or is it due to Windows itself ? > > As a workaround, it seems only parsing the output from > 'ps -Wl' could give me the desired functionality, which > is testing if a certain process, of which the PID is known, > is still running or not. > > Does anyone have maybe other ideas I might have > missed ? Depending on your user rights you might be unable to access the POSIX process information object created by Cygwin processes running in another session. This is a result of a change starting with Windows 2003 and XP 64 bit. The current solution in Cygwin is slighlty incorrect but we don't have a nice workaround so far. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/