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
From: Jeff Mincy <jeff AT delphioutpost DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15339.61133.650056.275129@delphioutpost.com>
Date: Fri, 9 Nov 2001 09:57:17 -0500
To: cygwin AT cygwin DOT com
Subject: Re: ssh: Write failed: The descriptor is a file, not a socket
In-Reply-To: <3BEBC7E8.CBA26EA9@syntrex.com>
References: <15339 DOT 18258 DOT 830000 DOT 776758 AT antarres DOT muniversal DOT com>
	<3BEBC7E8 DOT CBA26EA9 AT syntrex DOT com>
X-Mailer: VM 6.96 under 21.1 (patch 11) "Carlsbad Caverns" XEmacs Lucid

   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?

   
   >   ------------------------------------------------------------------------
   > The cygcheck output is attached:
   >    cygcheck.out       Type: unspecified type (application/octet-stream)
   >                   Encoding: base64
   >   ------------------------------------------------------------------------
   
   Now this looks kinda strange to me - the attached files has some
   garbage in it a two points - could that be some kind of bug in
   cygcheck ?! Does anyone see the garbage in the attached file as I
   do ?

It was trashed - should have overridden the default (& broken)
octet-stream content type.

-jeff

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