Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<3BEBF0BE.8A983D82@syntrex.com>
Date:	Fri, 09 Nov 2001 16:05:34 +0100
From:	Pavel Tsekov <ptsekov AT syntrex DOT com>
X-Mailer:	Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686)
X-Accept-Language:	en
MIME-Version:	1.0
To:	Jeff Mincy <jeff AT delphioutpost DOT com>
CC:	cygwin AT cygwin DOT com
Subject:	Re: ssh: Write failed: The descriptor is a file, not a socket
References:	<15339 DOT 18258 DOT 830000 DOT 776758 AT antarres DOT muniversal DOT com>
	<3BEBC7E8 DOT CBA26EA9 AT syntrex DOT com> <15339 DOT 61133 DOT 650056 DOT 275129 AT delphioutpost DOT com>

Jeff Mincy wrote:
> 
>    From: Pavel Tsekov <ptsekov AT syntrex DOT com>
>    Date: Fri, 09 Nov 2001 13:11:20 +0100
> 
>    Jeff Mincy wrote:
>    >
>    > I get "Write failed: The descriptor is a file, not a socket"
>    > when I try to do ssh X11 forwarding for the following command:
>    >     'ssh -X -f jeff AT delphioutpost DOT com xemacs'
>    >
>    > The contents of ssh -v output is attached:
> 
>    Ok you can look for more information on this topic and possible
>    solutions if you search the mailing list using "The descriptor is a
>    file, not a socket".
> 
>    [ ... ]
> 
> I had searched the archive for the entire
>   "Write failed: The descriptor is a file, not a socket"
> and got 5 hits (starting with my report of this problem in a snapshot)
> doing the search on
>   "descriptor is a file not a socket"
> gets ten pages of hits on rsync, inetd, postgres, cvs, getpeername.
> Is there a particular message that I'm missing?

Hehe, ok :) This seems to be a common problem on Win9x systems. The
suggested
solution generally was to upgrade to a recent CVS snapshot version of
cygwin1.dll
and see if it helps or upgrade to WinNT/2k/XP.

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