Searching Google with "duplicatehandle inherit socket handle bug",
I can find many pages which seems to be similar to this problem
in another server applications on Windows:
>This routine is neccessary to run socket applications on Win95 (I don't know
>if it neccessary for Win98). The problem is in socket() call on W95 - the
>socket returned is non-inherittable handle (unlike NT and Unixes, where
>sockets are inherittable). To fix the problem DuplicateHandle call is used
>to create inherittable handle, and original handle is closed. But,
>unfortunately, that raises a problem with winsock proxy dll.
> if the particular stacks' bug is that it won't associate a handle as a
> socket if that handle was duped with DuplicateHandle(). Other bugs with
If you see the same problem with Cygwin or Apache on your machines,
probably the problem with DeleGate is caused by the same reason.
The problem seems to be able to be described as "a socket handle duplicated
by DuplicateHandle() is not inherited to a child process, or it is not
recognized as a socket handle by a child process, on some WinSock
So I made a test version of DeleGate which does not do DuplicatHandle()
and placed it at "ftp://ftp.delegate.org/pub/DeleGate/tmp/dg860a.exe"
Could you test it like dg860a.exe -f -W4 -P8080 ADMIN=... ?
@ @ Yutaka Sato <email@example.com> http://www.delegate.org/y.sato/
( - ) National Institute of Advanced Industrial Science and Technology (AIST)
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller