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:	Wed, 21 May 2003 15:35:33 -0400
From:	Andrew MacKenzie <andy AT edespot DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: ssh-agent eats 80% cpu time
Message-ID:	<20030521193532.GJ3013@edespot.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>
Mime-Version:	1.0
In-Reply-To:	<20030521125746.GD920@cygbert.vinschen.de>
User-Agent:	Mutt/1.4.1i
Organization:	eDespot.com

--oy4uYLfziFOmrHBx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> > did it initially.
> > Also I made a strace with and without debug mode for ssh-agent.
> > In debug mode it is waiting for some input after a few moments.
> > Last lines read
> > [...]
> > 11430  825743 [main] ssh-agent 148 start_thread_socket: exitsock 0x358
> >   482  826225 [main] ssh-agent 148 start_thread_socket: stuff_start 0x2=
2FD24
> >  1262  827487 [select_socket] ssh-agent 148 thread_socket: stuff_start
> > 0x100F9BB4
> >   188  827675 [main] ssh-agent 148 select_stuff::wait: m 2, ms 42949672=
95
> >=20
> > And here it is waiting - this is okay.
> > 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".
I get this error message too when I use SSH to connect to a Linux box and
Solaris box (both running openssh servers).

This also seems to be causing a problem with rsync over ssh.  rsync doesn't
seem to like it at all.  I've posted to this before with the output, but
here it is in a nutshell again:

# rsync -e ssh -av MAGS amackenz AT edw450-1-1:.=20
amackenz AT edw450-1-1's password:=20
Warning: No xauth data; using fake authentication data for X11
forwarding.
channel 0: chan_shutdown_read: close() failed for fd-1: Socket operation on=
 non-socket
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
channel 0: chan_shutdown_write: close() failed for fd-1: Socket operation o=
n non-socket
rsync: read error: Connection reset by peer
rsync error: error in rsync protocol data stream (code 12) at
/tmp/rsync-2.5.6/io.c(177)


--=20
// Andrew MacKenzie  |  http://www.edespot.com
// GPG public key: http://www.edespot.com/~amackenz/public.key
// bonis nocet quisquis pepercerit malis.
// whoever spares the bad injures the good.

--oy4uYLfziFOmrHBx
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+y9UEEwWkWKWPRp8RAoj1AKCcLdcva6GfLXb0quy4clO22WiTqwCeI0AL
CjvpmNUpEg3GD80ZfxEW0R4=
=r4f+
-----END PGP SIGNATURE-----

--oy4uYLfziFOmrHBx--

- Raw text -