bug report - kill f || plea for help

Sat Mar 17 18:40:00 GMT 2001

On Sun, Mar 18, 2001 at 12:19:02PM +1100, Robert Collins wrote:
>Should this work ?
>>administrator@LIFELESSWKS ~
>$ ps
> PID PPID PGID WINPID TTY UID STIME COMMAND
> 2916 1 2916 2916 -1 500 12:10:20 /usr/bin/bash
> 1924 1 1924 1924 -1 500 12:10:21
>/usr/bin/ssh-agent
> 2480 2916 2480 2140 -1 500 12:10:22 /usr/bin/ps
>>administrator@LIFELESSWKS ~
>$ kill f 1924
>bash: kill: f: no such pid
>>I ask because I grabbed the code for using cygwin_external from the kill
>utility, and was a little surprised when it failed to give me data... I
>tracked it back to the functions in external.cc on a debug build of
>cygwin.

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'.
Hmm. That seems to be broken currently.
>So then I tried kill f .... which didn't work.
>>before you ask for patchs.... I'm offering one :] But not for this
>function :[
>>I'm a little lost here in the guts of cygwin, I'd _really_ appreciate a
>pointer -
>>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.
cgf
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple