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/

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

[InfoError90250]

Below is the result of your feedback form.  It was submitted by
 (InfoError90250@msn.com) on Saturday, May 25, 2002 at 08:42:53
---------------------------------------------------------------------------

message: Hey Big Boy!! ::Moans::\x7f\x7fI Feel So Good Right Now, Getting My Pussy Sucked By My Home Girl Lily!\x7f\x7f::Moans:: We Wanted To Know If You Wanted To Cum See Us For FREE!\x7f\x7fYou Have To Cum! Oh My God This Feels So Good!\x7f\x7fThe Website Address Is http://www.pornhome.com/lesbian/critik01/ourwebcam.htm\x7f\x7f\x7fIt Is 100% FREE, No Credit Card Needed, Or No Bullshit Downloads!\x7f\x7fHope To See You Soon!\x7f\x7fLove, Jen n Lily

---------------------------------------------------------------------------


--
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?!?

[Gerrit P. Haase]

Hallo InfoError90250,

Am Samstag, 25. Mai 2002 um 09:42 schriebst du:

SPAM, was reported to your provider by me.

-- 
=^..^=


--
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?!?

[Gerrit P. Haase]

SPAM, was reported:

http://spamcop.net/sc?id=z38685245zd4eda2d13248d49a8fb0c421bee78f84z

Gerrit
-- 
=^..^=


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

I'm all for reporting spam but remember if you report spam to the cygwin
mailing list and leave on the URLs at the bottom of each message, SpamCop
thinks that they might be part of the spam and sends me a nastygram since
http://cygwin.com/faq/ could be a reference to a porn site or something.

So, if possible, please strip the cygwin trailers from your report.

Also, there is no need to send two messages mentioning the spam here.
There is no need to send any replies whatsoever, in fact.  As I keep
saying, the spam is annoying enough without having to see repeated
references to it.

cgf

On Sat, May 25, 2002 at 12:30:16PM +0200, Gerrit P. Haase wrote:
>
>SPAM, was reported:
>
>http://spamcop.net/sc?id=z38685245zd4eda2d13248d49a8fb0c421bee78f84z
>
>Gerrit
>-- 
>=^..^=

--
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?!?

[Gerrit P. Haase]

Hallo Christopher,

Am Samstag, 25. Mai 2002 um 20:15 schriebst du:

> I'm all for reporting spam but remember if you report spam to the cygwin
> mailing list and leave on the URLs at the bottom of each message, SpamCop
> thinks that they might be part of the spam and sends me a nastygram since
> http://cygwin.com/faq/ could be a reference to a porn site or something.

Did you got messages from SpamCop?
As you can see here:
http://spamcop.net/sc?id=z38685245zd4eda2d13248d49a8fb0c421bee78f84z
I sent two messages to postmaster@exnis.net & postmaster@bob.exnis.net
and SpamCop usually is parsing just the headers.

Since it is really obvious that this is a list mail after reading the
headers I hope noone would be such a fool to put the list provider on
a blacklist.

Also I need to review the parsing after they finished it.
The abuse messages are only send out if I say "Send now".


> So, if possible, please strip the cygwin trailers from your report.

Nope, sorry, that is technical not possible.  I report what I get, the
complete message as attachment.

> Also, there is no need to send two messages mentioning the spam here.
> There is no need to send any replies whatsoever, in fact.  As I keep
> saying, the spam is annoying enough without having to see repeated
> references to it.

Ok, thats no problem.

Gerrit
-- 
=^..^=


--
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 Sat, May 25, 2002 at 08:39:25PM +0200, Gerrit P. Haase wrote:
>Hallo Christopher,
>
>Am Samstag, 25. Mai 2002 um 20:15 schriebst du:
>
>> I'm all for reporting spam but remember if you report spam to the cygwin
>> mailing list and leave on the URLs at the bottom of each message, SpamCop
>> thinks that they might be part of the spam and sends me a nastygram since
>> http://cygwin.com/faq/ could be a reference to a porn site or something.
>
>Did you got messages from SpamCop?

Not this time, no.  It has happened in the past.

>As you can see here:
>http://spamcop.net/sc?id=z38685245zd4eda2d13248d49a8fb0c421bee78f84z
>I sent two messages to postmaster@exnis.net & postmaster@bob.exnis.net
>and SpamCop usually is parsing just the headers.
>
>Since it is really obvious that this is a list mail after reading the
>headers I hope noone would be such a fool to put the list provider on
>a blacklist.
>
>Also I need to review the parsing after they finished it.
>The abuse messages are only send out if I say "Send now".
>
>
>> So, if possible, please strip the cygwin trailers from your report.
>
>Nope, sorry, that is technical not possible.  I report what I get, the
>complete message as attachment.

Ok.  If I do see some indication that someone is making my life harder
by reporting cygwin mailing lists as spam sources, they will be
unsubscribed and blocked from the cygwin mailing lists.

I'm all for reporting spam but I don't personally want to be doubly or
triply impacted by the spam.

So there's the new cygwin mailing list policy.  If I'm not bothered
by the likes of SpamCop then there is no problem.  Hopefully that
is the case here.

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/