[syslog-ng]1.4.11 fixes SIGHUP problems?
John_Delisle@ceridian.ca
John_Delisle@ceridian.ca
Mon, 12 Mar 2001 11:57:00 -0600
I'd say it does make sense, but the point was that not starting with a
broken config wasn't a bug. Output to stderr would be fantastic.
John Delisle
Corporate Technology
Ceridian Canada Ltd
204-975-5909
William Yodlowsky
<wyodlows@andromeda.ru To: syslog-ng@lists.balabit.hu
tgers.edu> cc:
Sent by: Subject: Re: [syslog-ng]1.4.11 fixes SIGHUP problems?
syslog-ng-admin@lists.
balabit.hu
2001/03/12 11:49 AM
Please respond to
syslog-ng
On Mon, Mar 12, 2001 at 12:47:33PM -0500, jon@dumbo.pobox.com wrote:
> IMO, it should dump to STDOUT/ERR as well...much like apachectl restart.
>
> apache says something like "config is broken, ignoring restart"
>
> i've made changes to the config file before(with errors) never thinking
there's a problem.
> logging continued normally, not error messages i could see.
I'm afraid I agree totally with this... I've done the same thing.
> not many people will want to have to check a log file after a restart,
they may think
> "telling it to HUP, didn't report any errors, and my other logs are still
there..."
>
> On Mon, Mar 12, 2001 at 11:33:35AM -0600, John_Delisle@ceridian.ca wrote:
> |
> |
> | I'm not sure thats a bug, it may be a feature actually. If you look at
> | /var/log/messages, theres an entry saying the new config is bad, and
> | syslog-ng will continue running with the old config. This prevents
lost
> | syslog messages.
_______________________________________________
syslog-ng maillist - syslog-ng@lists.balabit.hu
https://lists.balabit.hu/mailman/listinfo/syslog-ng