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: <3A15F92F.B594D82E@sattel.com>
Date: Fri, 17 Nov 2000 19:36:15 -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: syslog -> NT event logger mapping
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> 
> Bruce Edge wrote:
> >
> > 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.
> 
> I'm not sure if it's worth to change the openlog interface. It
> contains the identity as first parameter already.
> Wouldn't it be enough to add a registry key for an application to
> point to the Cygwin DLL as message file?

Sure. That would be great. 

> Personally I would favour to use always the one and only Cygwin
> registry key to avoid polluting the registry with entries for all
> Cygwin applications using syslog.

Agreed, unix apps should not be concerned with monkeying with the windows
registry.

-Bruce.

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