Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sat, 17 Mar 2001 22:21:17 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: bug report - kill f || plea for help Message-ID: <20010317222117.A6409@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <012901c0af49$6bae6ac0$0200a8c0@lifelesswks> <20010317214107.A23324@redhat.com> <017301c0af59$3d35f3b0$0200a8c0@lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <017301c0af59$3d35f3b0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Sun, Mar 18, 2001 at 02:12:16PM +1100 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 -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple