public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
To: Joseph Annino <jannino@jannino.com>, cygwin <cygwin@cygwin.com>
Subject: Re: Getting a process list from perl
Date: Wed, 29 May 2002 15:42:00 -0000	[thread overview]
Message-ID: <4.3.1.2.20020529145849.0262ffd8@pop.ma.ultranet.com> (raw)
In-Reply-To: <B91A8DE1.8D0D%jannino@jannino.com>

At 01:53 PM 5/29/2002, Joseph Annino wrote:
>Is there some reliable sanctioned method of getting the list of running
>processes, their group ids, and parent ids, from perl under cygwin?
>
>I asked a question earlier about cygwin getting very very slow after killing
>an rsync that spawns an SSH.  I don't get this problem if I kill the SSH
>instead.  So I need a way to get the pid of the ssh spawned by rsync so I
>can kill it.  And if anyone has any advice about the slowness problem let me
>know too.  Thanks.


How about ps?



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

      parent reply	other threads:[~2002-05-29 19:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-27  6:35 You ready for our blind date? Do you even know?!? Mark Sheppard
2002-05-27 22:19 ` Christopher Faylor
2002-05-29 14:14 ` Getting a process list from perl Joseph Annino
2002-05-29 14:43   ` Joseph Annino
2002-05-29 17:24     ` Michael A Chase
2002-05-30  1:24     ` Chris January
2002-05-31  4:20       ` Joseph Annino
2002-05-29 15:42   ` Larry Hall (RFK Partners, Inc) [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4.3.1.2.20020529145849.0262ffd8@pop.ma.ultranet.com \
    --to=lhall@rfk.com \
    --cc=cygwin@cygwin.com \
    --cc=jannino@jannino.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).