This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: OpenSSH 2.3.0p1 Win98 listen: No buffer space available; the socket cannot be connected
- To: "Jari Aalto+list.cygwin" <posting-list at MailAndNews dot com>, <cygwin at sourceware dot cygnus dot com>
- Subject: RE: OpenSSH 2.3.0p1 Win98 listen: No buffer space available; the socket cannot be connected
- From: "Dr. Carsten Bormann" <cabo at tzi dot org>
- Date: Sun, 17 Dec 2000 09:12:14 +0100
I assume you run 1.1.6?
This looks very similar to the problem I have reported under the thread
"OpenSSH + 1.1.6 strangely wedges W98SE networking".
There seems to be a resource leak somewhere; as I reported I can get about
42 SSH tunnels opened before things wedge.
Gruesse, Carsten
> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Jari
> Aalto+list.cygwin
> Sent: Sunday, December 17, 2000 04:38
> To: cygwin@sourceware.cygnus.com
> Subject: OpenSSH 2.3.0p1 Win98 listen: No buffer space available; the
> socket cannot be connected
>
>
>
> After several uses of the ssh-agent in every opened bash window
> (5-10), I sart getting these errors. There should be loads of
> memory available (200M virtual, 70M Real)
>
> Where is this error coming from?
>
> //jaalto@PICASSO /cygdrive/c/WINDOWS/Työpöytä $ _
> listen: No buffer space available; the socket cannot be connected
>
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com