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. John Delisle Corporate Technology Ceridian Canada Ltd 204-975-5909 jon@dumbo.pobox.com Sent by: To: syslog-ng@lists.balabit.hu syslog-ng-admin@lists. cc: balabit.hu Subject: Re: [syslog-ng]1.4.11 fixes SIGHUP problems? 2001/03/12 11:21 AM Please respond to syslog-ng i noticed one problem. if the configuration file is broken to the point syslog-ng will not start, HUP does not notice this ie. if you forget a semicolon somewhere kill -HUP syslog-ng-pid works w/o erros but kill syslog-ng-pid and syslog-ng dies... y On Fri, Mar 09, 2001 at 10:01:08AM +0100, Balazs Scheidler wrote: | Hi, | | I was wondering whether the 1.4.11 release did really fix the SIGHUP | problems many of you encountered? Some feedback would be useful. | | TIA, | -- | Bazsi | PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 | | _______________________________________________ | syslog-ng maillist - syslog-ng@lists.balabit.hu | https://lists.balabit.hu/mailman/listinfo/syslog-ng _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng