RE: [PATCH] EventLog display name patch

2003-06-18 Thread William A. Rowe, Jr.
At 03:04 PM 6/18/2003, Juan Rivera wrote: >Is there any other way to get the display name? I look for other ways but couldn't >figure out another approach. From the registry. It just looks like we look up the display name a little too late for some classes of errors. Working on this. Bill

RE: [PATCH] EventLog display name patch

2003-06-18 Thread Juan Rivera
Title: RE: [PATCH] EventLog display name patch Is there any other way to get the display name? I look for other ways but couldn't figure out another approach. Juan -Original Message- From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 18, 2003 3:43

Re: [PATCH] EventLog display name patch

2003-06-18 Thread William A. Rowe, Jr.
At 09:59 AM 6/18/2003, Juan Rivera wrote: >The current nt_eventlog implementation has the hardcoded "Apache Service" as the >event log application name. This can be problematic if you have multiple instances of >Apache running on the same box. > >To fix this, I made midifications on two files:

RE: [PATCH] EventLog display name patch

2003-06-18 Thread Juan Rivera
Title: [PATCH] EventLog display name patch BTW, the service.c patch should also take care of the following bug. If your configuration file has a syntax error, you will get something like this in your event log:   The Apache service named  reported the following error: >>> Syn

[PATCH] EventLog display name patch

2003-06-18 Thread Juan Rivera
Title: [PATCH] EventLog display name patch The current nt_eventlog implementation has the hardcoded "Apache Service" as the event log application name. This can be problematic if you have multiple instances of Apache running on the same box. If, for instance, you register multi