On 18 Aug 2004 at 15:25, Jay Fenlason wrote: > I've been trying to debug why Amanda won't work under cygwin for me > any more, and I've traced it down to a socket() call in the sendbackup > program. strace shows the following (massively snipped) > > 709 258623 [main] sendbackup 628 cygwin_socket: socket (2, 1, 6) > 79416 338039 [main] sendbackup 628 wsock_init: res 0 > 281 338320 [main] sendbackup 628 wsock_init: wVersion 514 > 140 338460 [main] sendbackup 628 wsock_init: wHighVersion 514 > 352 338812 [main] sendbackup 628 wsock_init: szDescription WinSock > 2.0 147 338959 [main] sendbackup 628 wsock_init: szSystemStatus > Running 134 339093 [main] sendbackup 628 wsock_init: iMaxSockets 0 > 135 339228 [main] sendbackup 628 wsock_init: iMaxUdpDg 0 138 > 339366 [main] sendbackup 628 wsock_init: lpVendorInfo 0 > 8525 347891 [main] sendbackup 628 __set_winsock_errno: > cygwin_socket:602 - winsock error 10106 -> errno 1 > 263 348154 [main] sendbackup 628 cygwin_socket: -1 = socket (2, 1, > 6) > > but I've no clue how to debug further than this. The socket call > socket ( PF_INET, SOCK_STREAM, IPPROTO_TCP ) looks OK to me. . . > > -- JF > > P.S. "strace -o foo ./amandad.exe" will silently run /bin/amanda.exe > instead of the one in your current directory. Perhaps the man page > needs a stronger warning about legal pathnames for executables. :-)
I am wondering if the latest cygwin has real trouble somewhere in its socket creation. Yours + these two seem to suggest there is a problem. http://www.cygwin.com/ml/cygwin/2004-08/msg00452.html http://www.cygwin.com/ml/cygwin/2004-08/msg00479.html I am wondering if the fix Corinna implemented for ssh might be relevant. - http://www.cygwin.com/ml/cygwin/2004-08/msg00702.html. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
