Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <017f01c0af5a$e803e260$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>
References: <012901c0af49$6bae6ac0$0200a8c0@lifelesswks> <20010317214107.A23324@redhat.com> <017301c0af59$3d35f3b0$0200a8c0@lifelesswks> <20010317222117.A6409@redhat.com>
Subject: Re: bug report - kill f || plea for help
Date: Sun, 18 Mar 2001 14:24:12 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin@cygwin.com>
Sent: Sunday, March 18, 2001 2:21 PM
Subject: Re: bug report - kill f || plea for help


> On Sun, Mar 18, 2001 at 02:12:16PM +1100, Robert Collins wrote:
> >>It's pretty simple:
> >>
> >>pinfo p (pid);
> >>
> >>>The external_pinfo struct contains what I need, so if it's easier
to
> >>>get that that, that's fine (and thats why I grabbed the code from
> >>>kill).
> >>
> >>The external_pinfo struct is intended for external use.  It's not
> >>intended to be called from inside cygwin.
> >
> >can pinfo p (pid) return information on non-cygwin processes?  It
would
> >really be neat for things like renice to affect non-cygwin programs
as
> >well...
>
> No.  pinfo is for manipulating the pids of cygwin processes.  Most of
the
> time these are != to windows pids, unfortunately, although they do
represent
> the windows pid of a forked child.
>
> cgf
>

Ah well. I'll note that in the code.

Thanks a lot, the whole things working... Mailing the patch in in about
5 mins..

Rob


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple