Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <017301c0af59$3d35f3b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>
References: <012901c0af49$6bae6ac0$0200a8c0@lifelesswks> <20010317214107.A23324@redhat.com>
Subject: Re: bug report - kill f || plea for help
Date: Sun, 18 Mar 2001 14:12:16 +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 1:41 PM
Subject: Re: bug report - kill f || plea for help


> On Sun, Mar 18, 2001 at 12:19:02PM +1100, Robert Collins wrote:
> >administrator@LIFELESSWKS ~
> >$ kill f 1924
> >bash: kill: f: no such pid
> >
>
> I don't understand.  Why would you expect 'f' to mean anything?  If
> I do "kill f" on linux I get:
>
>     % kill f
>     kill: illegal pid: f
>
> I think you probably mean 'kill -f'.

Yes. Oops.

> Hmm. That seems to be broken currently.
>
> >
> >What I coding is within the cygwin dll, I need to end up with
> >(preferrably) a filled out pinfo struct for a passed pid. Doing it
for
> >the current process is easy enough, but how do I retrieve the info
for
> >other processes?
>
> 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...

Rob


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