Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Envelope-To: cygwin AT cygwin DOT com Message-ID: <2592.212.0.200.22.1061395373.mtc@mail.moldtelecom.md> Date: Wed, 20 Aug 2003 19:02:53 +0300 (EEST) Subject: Re: accept doesn't block while running as NT service From: linamat AT moldtelecom DOT md To: cygwin AT cygwin DOT com User-Agent: Moldtelecom Mail System MIME-Version: 1.0 Content-Type: text/plain;charset=windows-1251 X-Priority: 3 Importance: Normal Note-from-DJ: This may be spam SYSTEM can use network resources without doubts, because UNIX domain socket works under NT service, inetd also works as NT service. Turning to accept() problem errno was set to EBADF. I parsed fhandler_socket.cc's method accept(); there are 2 places where EBADF might be set: 1st after sock_event handling if blocking (but I use FASYNC | O_NONBLOCK), 2nd after ancestor's accept() which checks for invalid handle. It seems that socket descriptor is suddenly closed or invalidated under NT service. I've even tried to run some very simple TCP socket servers through SCM, but it fail. Don't forget that all OK with it while it runs from console as application. Is such behaveour normal? -- 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/