Winsock closesocket() problem

[Pierre A. Humblet]

Jason,

in your test case the setuid is called after the initial socket().
Thus it is conceivable that the impersonated thread (after setuid) 
cannot always access the socket.

However when you first brought up the issue with exim, setuid()
occurs before socket().
Also exim can send and receive on those sockets, the only problem
is in closing them.

Just adding info, not explaining anything :(

Pierre