Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 18 Nov 2002 23:57:54 -0500
From:	Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ramped CPU problem with fetchmail
Message-ID:	<20021119045754.GC28126@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20021118211434 DOT 020a1458 AT localhost>
Mime-Version:	1.0
In-Reply-To:	<5.2.0.9.2.20021118211434.020a1458@localhost>
User-Agent:	Mutt/1.5.1i

On Mon, Nov 18, 2002 at 09:32:47PM -0700, Christian Weeks wrote:
>Output from:
>fetchmail --version:
>This is fetchmail release 6.1.2+NTLM+SSL+NLS
>Fallback MDA: /usr/bin/procmail -d %T
>CYGWIN_NT-5.1 CWEEKS-LAP 1.3.15(0.63/3/2) 2002-11-07 13:57 i686 unknown
>Taking options from command line and /home/cpw/.fetchmailrc
>Logfile is /var/log/fetchmail.log
>Idfile is /home/cpw/.fetchids
>
>Other info is attached.
>
>Problem summary:
>
>It appears that the CPU ramp problem with emacs that has been discussed on 
>this mailing list is not restricted to emacs.

So why aren't you trying the solution that was proposed for the problem?

This is, what?, the third time today that someone has posted saying that
they've noticed the discussion while missing the fact that the problem
is supposed to be fixed in the latest snapshots.

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/

- Raw text -