re: ssh: Write failed: The descriptor is a file, not a socket

re: ssh: Write failed: The descriptor is a file, not a socket

[Jeff Mincy]

BTW,  The problem reported in 

  http://cygwin.com/ml/cygwin/2001-11/msg00493.html

with ssh getting a socket 'ENOTSOCK' error is fixed in
cygwin-1.3.5-1

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

re: ssh: Write failed: The descriptor is a file, not a socket

[Jeff Mincy]

BTW,  The problem reported in 

  http://cygwin.com/ml/cygwin/2001-11/msg00493.html

with ssh getting a socket 'ENOTSOCK' error is fixed in
cygwin-1.3.5-1

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

ssh: Write failed: The descriptor is a file, not a socket

[Jeff Mincy]

[-- Attachment #1: Type: text/plain, Size: 214 bytes --]

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@delphioutpost.com xemacs'

The contents of ssh -v output is attached:

[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 13444 bytes --]

Re: ssh: Write failed: The descriptor is a file, not a socket

[Pavel Tsekov]

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@delphioutpost.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".

[ ... ]

>   ------------------------------------------------------------------------
> 
> The cygcheck output is attached:
> 
>   ------------------------------------------------------------------------
>                       Name: cygcheck.out
>    cygcheck.out       Type: unspecified type (application/octet-stream)
>                   Encoding: base64
>                Description: cygcheck output
> 
>   ------------------------------------------------------------------------

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 ?

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

Re: ssh: Write failed: The descriptor is a file, not a socket

[Mark Himsley]

On Fri, 09 Nov 2001 13:11:20 +0100 you wrote:

>> The cygcheck output is attached:
>> 
>
>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 ?

I think the attachment is corrupt.

-- 
Mark Himsley
In Acton

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

Re: ssh: Write failed: The descriptor is a file, not a socket

[Jeff Mincy]

   From: Pavel Tsekov <ptsekov@syntrex.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@delphioutpost.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/

Re: ssh: Write failed: The descriptor is a file, not a socket

[Pavel Tsekov]

Jeff Mincy wrote:
> 
>    From: Pavel Tsekov <ptsekov@syntrex.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@delphioutpost.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/

Re: ssh: Write failed: The descriptor is a file, not a socket

[Pavel Tsekov]

Jeff, can you run cygcheck again and send the output to the maling list
or to me personally since the previous one seemed to be corrupt.

Jeff Mincy wrote:
> 
>   ------------------------------------------------------------------------
> 
> The cygcheck output is attached:
> 
>   ------------------------------------------------------------------------
>                       Name: cygcheck.out
>    cygcheck.out       Type: unspecified type (application/octet-stream)
>                   Encoding: base64
>                Description: cygcheck output
> 
>   ------------------------------------------------------------------------

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

Re: ssh: Write failed: The descriptor is a file, not a socket

[Jeff Mincy]

   From: Pavel Tsekov <ptsekov@syntrex.com>
   Date: Fri, 09 Nov 2001 13:43:29 +0100
   
   Jeff, can you run cygcheck again and send the output to the maling list
   or to me personally since the previous one seemed to be corrupt.
   
   Jeff Mincy wrote:
   >   ------------------------------------------------------------------------
   > The cygcheck output is attached:
   >    cygcheck.out       Type: unspecified type (application/octet-stream)
   >                   Encoding: base64
   >   ------------------------------------------------------------------------

Sorry, the attachment was trashed.  Seems to be a
windows/xemacs/problem that I'll track down eventually.
-jeff