This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: syslog -> NT event logger mapping

/speaking from ignorance

what about the insertion strings? Can't cygwin just have a single message
file with a single message, that is nothing but an insertion string?

If it needs to be registered for each, well that could be a simple
register_syslog exefile.exe

And yes I'd be willing to put some effort into making it happen.


----- Original Message -----
From: "Corinna Vinschen" <>
To: "cygwin" <>
Sent: Friday, November 17, 2000 9:43 PM
Subject: Re: syslog -> NT event logger mapping

> Bruce Edge wrote:
> >
> > I think it's great that syslog works under cygwin, but I have a question
> > the events that are logged.
> > They all start with:
> >
> > "The description for Event ID ( 0 ) in Source ( LCBD ) could not be
found. It
> > contains the following insertion string(s):"
> > [...]
> > Is there a way to get rid of the extra garbage at the beginning of the
> > message?
> Not an easy way I know of. The problem here is the way the syslog is
> organized in NT. A part of the syslog entry (and unfortunately the most
> important one) is a pointer into a message file which contains the
> _real_ log text. The log text which you are interested in is only a sort
> of comment. The name of the message file has to be stored in the registry.
> You would need an entry there for each application which uses the syslog
> facility.
> However, there _is_ a way but it's work.
> Corinna
> --
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer              
> Red Hat, Inc.
> --
> Want to unsubscribe from this list?
> Send a message to

Want to unsubscribe from this list?
Send a message to

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]