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
Message-ID:	<000401c3236a$806dc950$42529a09@IBMJY56AED2CIQ>
From:	"Heinz Peter Hippenstiel" <hhippenstiel AT gmx DOT net>
To:	<cygwin AT cygwin DOT com>
References:	<1053502004 DOT 18017 DOT ezmlm AT cygwin DOT com> <000b01c31f71$acbd04a0$42529a09 AT IBMJY56AED2CIQ> <20030521090507 DOT GE30676 AT cygbert DOT vinschen DOT de> <000f01c31f8b$674ed280$42529a09 AT IBMJY56AED2CIQ> <20030521125746 DOT GD920 AT cygbert DOT vinschen DOT de>
Subject:	Re: ssh-agent eats 80% cpu time
Date:	Mon, 26 May 2003 11:37:57 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1165

> > Without -d it is not waiting but waking up after a few moments and this
> > loops endlessly (see strace.txt). That's why it's eating up the CPU.
> > Question is why it is not waiting?
>
> I see the reason but not why it happens :-(  The error message is
> something like "socket operation on non-socket".

Question is where is the difference running the ssh-agent in debug mode to
the normal mode?
Ok, it's the debug mode - of course ... but the functionality stays the
same.

Kind regards, HP


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