Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Inetd running slow
Date:	Tue, 8 Nov 2005 16:36:24 -0000
MIME-Version:	1.0
In-Reply-To:	<4370D28A.5000802@cygwin.com>
Message-ID:	<SERRANONBDpJvDiVYKQ00000220@SERRANO.CAM.ARTIMI.COM>

Larry Hall (Cygwin) wrote:
> Stephen Patterson wrote:
>> Hi all
>> 
>> I've installed inetutils & uw-imapd on cygwin, registered inet as a
>> windows XP service (which starts OK) and I'm running uw-imapd through
>> inetd. Inetd & uw-imap are slow to respond when I connect to them
>> locally. 

>> Does anyone know what could be causing these messages?
> 
> 
> Yes, they are generated by 'inetd' starting and the initialization of
> the 'imap' service.  These are informational messages.  You don't need
> to be concerned about them.


  Which leaves us still with the "slow to respond" problem to understand.

  How slow to respond actually are they?  Is your PFW or AV software
interfering perhaps?  Or is uw-imap equally slow to respond when fired up from
the command line?


    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/

- Raw text -