What if the service isn't started manually? If it were set to start automatically when the machine starts, would you expect a message box?
What happens if there's some other problem on system startup and the event log is full? I've never tried that :) G. -- Graeme Foster ([EMAIL PROTECTED]) Principal Software Engineer Aston Broadcast Systems Ltd. (http://www.aston.tv) Disclaimer: I really don't have a clue what I'm on about. -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Urs Eichmann Sent: 16 October 2002 09:13 To: [EMAIL PROTECTED] Subject: Re: .NET Windows Services won't start if event log is full? > This is an interesting question about what the appropriate behavior > should be, though at a minimum you should get a decent error. I agree with that, there should be a messagebox popping up saying that the event log is full. What happens now if the event log is full is: The service just hangs in the services panel, displaying "starting service" for ever. ***************************************************************************** The contents of this email and any attachments are confidential. It is intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to any one or make copies. ** eSafe scanned this email for viruses, vandals and malicious content ** ***************************************************************************** You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
