This is the mail archive of the
mailing list for the Cygwin project.
Re: socket() function fails when application runs as an NT service.
> On Sun, 15 Sep 2002, Tom Cashmore wrote:
> Hi im having a strange problem with an application im writing using
> (v1.3.12-1 On win2k Sp3). If the application is run as a console app (Ie
> started from a cmd window) its able to open sockets (socket function
> a valid handle) but when the application is run as an NT service it is
> unable to succesfuly open sockets (Ie the socket function returns 0). Even
> if i place a socket function before the call to StartServiceCtrlDispatcher
> the socket function will still return a 0. This happens with the service
> running as both system and local admin. Im pretty much stumped and am
> that someone else may have been able to resolve this problem in the past.
> Any help would be greatly appreciated. Thank you.
> Tom Cashmore
I think 0 is a valid socket descriptor. -1 is not.
May be in a service there is no console, so descriptors 0, 1 and 2 are
closed, and the first new descriptor is 0.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html