This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Syslog "event source" registration [Was Re: Suggest cygrunsrv extension: --pidfile option (patch included)]
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 30 Nov 2005 17:14:26 -0800
- Subject: Re: Syslog "event source" registration [Was Re: Suggest cygrunsrv extension: --pidfile option (patch included)]
- References: <4380AB2E.7010302@t-online.de> <20051121153016.GI2999@calimero.vinschen.de> <438221C6.1080103@t-online.de> <20051122095442.GL2999@calimero.vinschen.de> <4384E07F.6000308@t-online.de> <20051124113107.GC2999@calimero.vinschen.de> <1EfHhO-1i3eWO0@fwd33.aul.t-online.de> <4385CE09.D2DAB8AF@dessent.net> <Pine.GSO.4.63.0511301836320.13483@slinky.cs.nyu.edu>
- Reply-to: cygwin at cygwin dot com
Igor Pechtchanski wrote:
> Why complicate openlog()? Let the Cygwin applications that use openlog()
> do this (e.g., in a postinstall script). We could even add a utility
> package in "Base", similar to "editrights", that contains scripts for
> adding and removing this setting (something like 'regtool add
> "KEY/$1/VAL"; regtool set "KEY/$1/VAL" "value"') that the postinstall and
> preremove scripts can invoke... That way this would also be cleaned up
> if, say, "openssh" were uninstalled.
That is certainly a reasonable alternative. Though it's slightly less
automatic since it requires every package maintainer of any program that
writes to the event log to do something in a postinstall (and presumably
preremove) script. But if it were turnkey to the point of being able to
just run "add-event-source sshd" in a postinstall, then it wouldn't be
too much hassle, and the user could even do it manually if necessary.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/