Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3A15D079.E4580042@sattel.com>
Date: Fri, 17 Nov 2000 16:42:33 -0800
From: Bruce Edge <bedge AT sattel DOT com>
Organization: Sattel Global Networks
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.15-4mdk i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin AT sources DOT redhat DOT com
Subject: Re: syslog -> NT event logger mapping
References: <3A14D32A DOT B5869866 AT sattel DOT com> <3A150BD3 DOT C44D46A0 AT redhat DOT com> <006a01c05087$b1d0ebc0$f7c723cb AT lifelesswks> <3A151760 DOT A3D339F6 AT redhat DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

How about using openlog() to determine how to handle this?
I'm not sure I can suggest which argument to openlog() could be used to
provide some sort of hint to cygwin as to how the app wanted to handle this
issue. 
Perhaps extend the openlog API to take a filename which would specify the
insertion string map file.
Of course this would involve a registry write on app startup to get the
message file name into the registry.

Incidentally, the LOG_CONS and LOG_PERROR don't seem to work.

-Bruce.

Corinna Vinschen wrote:
> 
> Robert Collins wrote:
> >
> > /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?
> 
> Yes, that's the way I was talking of.
> 
> > If it needs to be registered for each, well that could be a simple
> > register_syslog exefile.exe
> 
> The RegisterEventSource call currently uses the process_ident
> from `openlog' as identifier. This would have to be changed so
> that always "Cygwin" is the identifier and then there would be
> only one entry needed in the registry, the "Cygwin" subkey which
> points to the DLL which in turn contains the one and only (empty)
> message string. The process_ident would become a part of the
> comment string only.
> 
> > And yes I'd be willing to put some effort into making it happen.
> 
> I'm happy to read this :-))
> 
> BTW: I have just made a tiny change in syslog.cc. It now adds the
> user SID to the event log so that the name of the user is displayed
> instead of N/A (assuming `ntsec' is on).
> 
> 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

-- 
What this country needs is a good five cent ANYTHING!

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com