RE: cygwin processes and system'ed processes using 100% CPU

["Dave Korn" <dk at artimi dot com>]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Steven Hartland
> Sent: 27 January 2004 16:49
> To: cygwin@cygwin.com
> Subject: Re: cygwin processes and system'ed processes using 100% CPU
> 
> Sorry did I miss something where was the new issue?
> 
>     Steve

  Here's (some of) the headers from your first post with the current subject
line:

---snip---
Message-ID: <01c601c3e4e3$f186d380$b3db87d4@multiplay.co.uk>
From: "Steven Hartland" <[REDACTED EMAIL ADDRESS]>
To: <[REDACTED EMAIL ADDRESS]>
References: <40164D3D.3080601@dynaware.de>
<20040127122719.GH2120@bln.sesa.de>
<Pine.GSO.4.56.0401270841580.2972@slinky.cs.nyu.edu>
Subject: cygwin processes and system'ed processes using 100% CPU
Date: Tue, 27 Jan 2004 14:43:35 -0000
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_01C3_01C3E4E3.F173C0B0"
---snip---

  The 'references' header shows that rather than starting a new mail and
entering the address of the ML in the To: field, you took the shortcut of
opening a mail you'd just received, hitting Reply, and replacing the subject
and contents with a new one.  The mail you replied to is this one from the
scp thread:

http://cygwin.com/ml/cygwin/2004-01/msg01171.html

  Although some mailers, notably M$ ones, display the threading of posts
based purely on the Subject: header, others respect the References: header
and therefore place your post in the same thread as the one you were
replying to, even though you changed the subject.

  Using reply rather than starting a fresh mail is a natural enough way to
save yourself a bit of typing, but there's a bit of hidden persistent state
in there that not everyone knows about!



    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....
 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/