From: Joseph Annino <jannino@jannino.com>
To: Chris January <chris@atomice.net>, cygwin <cygwin@cygwin.com>
Subject: Re: Getting a process list from perl
Date: Fri, 31 May 2002 04:20:00 -0000 [thread overview]
Message-ID: <B91C540E.8E51%jannino@jannino.com> (raw)
In-Reply-To: <005801c2076f$168c8f70$0100a8c0@advent02>
Thanks for that. I'll look forward to having /proc around, and the
hopefully the Proc modules for perl will be updated shortly after to support
Cygwin's version of /proc.
Yes everyone, I know about ps, but parsing ps puts you in a rather system
dependant nightmare, and ps is columnar so sometimes it truncates data you
might need. I have O'Reilly's Perl for Sys Admins which has a nice little
chapter about process management. Anyhow, ps is there in a pinch.
Thanks.
On 5/29/02 8:15 PM, "Chris January" <chris@atomice.net> wrote:
>> Well I solved my own problem. When in doupt, upgrade. Going to the
> newest
>> version of rsync has solved my slowness problems so far. My perl signal
>> handler that kills all the scripts children is able to gracefully kill an
>> rsync that is taking too long, returning control back to the script so it
>> can clean up and finish somewhere outside the signal handler.
>>
>> I am still curious about getting process listings, since I will have use
> for
>> that still.
> Wait for Cygwin 1.3.11 when you will be able to get a directory listing of
> /proc. The all-numerical entries in that directory are process IDs.
>
> Regards
> Chris
>
>
>
> --
> 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/
>
--
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/
next prev parent reply other threads:[~2002-05-31 2:11 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 [this message]
2002-05-29 15:42 ` Larry Hall (RFK Partners, Inc)
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=B91C540E.8E51%jannino@jannino.com \
--to=jannino@jannino.com \
--cc=chris@atomice.net \
--cc=cygwin@cygwin.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).