On Tue, Nov 29, 2011 at 02:08:18PM +0530, Jaswinder Bhamra wrote:
>Hi,
>
>There was a post http://cygwin.com/ml/cygwin/2011-09/msg00017.html to
>which I got a reply "the fix is not yet available, but the fix will be
>in the next Cygwin release".
>Approximately when can I expect that, or is the fix
On Sep 5 08:08, Andrey Repin wrote:
> > However, even with this fix, you might not get EHOSTUNREACH either. In
> > my testing, the error returned by the underlying Winsock getsockopt
> > function is not WSAEHOSTUNREACH, but WSAETIMEDOUT. This will be
> > translated into ETIMEDOUT == "Connection
Greetings, Corinna Vinschen!
> However, even with this fix, you might not get EHOSTUNREACH either. In
> my testing, the error returned by the underlying Winsock getsockopt
> function is not WSAEHOSTUNREACH, but WSAETIMEDOUT. This will be
> translated into ETIMEDOUT == "Connection timed out".
To
On Sep 2 10:16, Jaswinder Bhamra wrote:
> Since RedHat machine is behind a firewall (defined by the rules in
> 'Linux Firewall.txt') I am expecting my program to give "No route to
> host" error (shown in cyggso.out-1.5.24-2.txt file) and not "Operation
> not permitted" (shown in cyggso.out-1.7.7-1
4 matches
Mail list logo
