> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Luis Lavena > Sent: Sunday, May 14, 2006 11:55 PM > To: [email protected] > Subject: Re: [Mongrel] Broken win32 service support for > lastest mongrels. > > > On 5/15/06, Zed Shaw <[EMAIL PROTECTED]> wrote: > [snip] > > One question, if the service stops then what about just not caring > > about the error? If it doesn't actually stop the system from > > functioning, we can probably just ignore it. > > The problem is that sometimes... that depends on windows > mood. I have seen a few times that after you got the broken > pipe error, the offending process (the service) is still > running, but don't answer via http nor any attempts to stop it again. > > Besides, average users will use the Service Manager to handle > the service, which will show error messages (and we didn't > talk about eventlog!). > > If we could fix it, less reports about that problem will > raise in the future and we wil get a better user experience overall...
I've forwarded this to the win32utils-devel list to see if anyone has any insight. Oh, and I should mention that I'm working on a pure Ruby version of win32-eventlog. I hope to have it out in the next couple of weeks. Regards, Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. _______________________________________________ Mongrel-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/mongrel-users
