RE: You ready for our blind date? Do you even know?!?

RE: You ready for our blind date? Do you even know?!?

[Mark Sheppard]

Christopher Faylor wrote:
> On Sat, May 25, 2002 at 08:39:25PM +0200, Gerrit P. Haase wrote:
> >
> >Did you got messages from SpamCop?
>
> Not this time, no.  It has happened in the past.

If you went to the SpamCop report and clicked "innocent bystander"
I'm pretty sure that you won't hear from SpamCop again (on the
address you use for the admin & tech contacts for cygwin.com) even
if people don't strip the URL from reported spam.

Mark.

--
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/

Re: You ready for our blind date? Do you even know?!?

[Christopher Faylor]

On Mon, May 27, 2002 at 10:06:59AM +0100, Mark Sheppard wrote:
>Christopher Faylor wrote:
>>On Sat, May 25, 2002 at 08:39:25PM +0200, Gerrit P.  Haase wrote:
>>>
>>>Did you got messages from SpamCop?
>>
>>Not this time, no.  It has happened in the past.
>
>If you went to the SpamCop report and clicked "innocent bystander" I'm
>pretty sure that you won't hear from SpamCop again (on the address you
>use for the admin & tech contacts for cygwin.com) even if people don't
>strip the URL from reported spam.

Yes, I *am* capable of reading information on a web page.

The point is that I don't want people reporting the cygwin mailing list
as a spam source.  Apparently this is a very hard concept for people to
understand.

cgf

--
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/

Getting a process list from perl

[Joseph Annino]

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.


--
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/

Re: Getting a process list from perl

[Joseph Annino]

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.

On 5/29/02 1:53 PM, "Joseph Annino" <jannino@jannino.com> 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.


--
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/

Re: Getting a process list from perl

[Michael A Chase]

On Wed, 29 May 2002 14:20:49 -0400 Joseph Annino <jannino@jannino.com> wrote:

> I am still curious about getting process listings, since I will have use for
> that still.

Have you tried piping from ps?
-- 
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



--
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/

Re: Getting a process list from perl

[Chris January]

> 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/

Re: Getting a process list from perl

[Joseph Annino]

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/

Re: Getting a process list from perl

[Larry Hall (RFK Partners, Inc)]

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/