Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <3A150BD3.C44D46A0@redhat.com> Date: Fri, 17 Nov 2000 11:43:31 +0100 From: Corinna Vinschen Reply-To: cygwin AT sources DOT redhat DOT com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin Subject: Re: syslog -> NT event logger mapping References: <3A14D32A DOT B5869866 AT sattel DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bruce Edge wrote: > > I think it's great that syslog works under cygwin, but I have a question about > 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 mailto:cygwin AT sources DOT redhat DOT com Red Hat, Inc. mailto:vinschen AT redhat DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com