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 Date: Thu, 22 Jan 2004 11:15:47 +0100 From: Corinna Vinschen To: Cygwin Subject: Re: Win XP crash with inetd Message-ID: <20040122101547.GF1831@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: Cygwin References: <400FA057 DOT 4020108 AT gamma-rs DOT ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <400FA057.4020108@gamma-rs.ch> User-Agent: Mutt/1.4.1i Since Cygwin is doing nothing which should result in a BSOD, I doubt that Cygwin is the actual cause of that problem. So far I never experienced a BSOD which I could trace back to Cygwin or inetd or it's services. Actually I never had a BSOD since I'm using XP. Corinna On Jan 22 11:05, Charles L. Werner wrote: > I forgot to include the Error message in the XP event viewer from inetd > prior to the crash: > > The description for Event ID ( 0 ) in Source ( inetd ) cannot be found. The > local computer > may not have the necessary registry information or message DLL files to > display messages > from a remote computer. You may be able to use the /AUXSOURCE= flag to > retrieve this description; > see Help and Support for details. The following information is part of the > event: inetd : PID 1892 : uucp/tcp: No such user 'uucp', service ignored. > > -- > Dr. Charles L. Werner > Gamma Remote Sensing AG > Thunstrasse 130 > CH-3074 Muri b. Bern, Switzerland > > Tel: +41 31 951 70 05 > FAX: +41 31 951 70 08 > http://www.gamma-rs.ch > > Date: Thu, 22 Jan 2004 10:35:20 +0100 > From: "Charles L. Werner" > Subject: Win XP crash with inetd ftp server > To: cygwin AT cygwin DOT com > Reply-To: cwATgamma-rsDOTch > > My XP Professional SP1 system had a kernel crash apparently related to > the tcpip, related I believe to the inetd service running > Here is the event information > > Symbolic name: > ER_KRNLCRASH_LOG > Error code 0000004e, parameter1 00000002, parameter2 00000058, parameter3 > 0007ff2f, parameter4 00000001. > > The network adapter os a 3Com Gigabit LOM (3c940) > > Attached is the cygcheck -svr and the output of netstat -a > > Have others experienced system crashes with the cygwin inetd service? > this has happened several times. > > When I disabled the inetd service, the sudden crashes ceased. > > Regards, > Charles > > > -- > Dr. Charles L. Werner > Gamma Remote Sensing AG > Thunstrasse 130 > CH-3074 Muri b. Bern, Switzerland > > Tel: +41 31 951 70 05 > FAX: +41 31 951 70 08 > > > -- > 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/ -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/