From f42b66df986e7a7eb617841ee5550ffbad567449 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 24 Oct 2005 08:04:57 +0000 Subject: made sure no call to exit or die is done once rsyslogd is running --- NEWS | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'NEWS') diff --git a/NEWS b/NEWS index 7d15e282..20489427 100644 --- a/NEWS +++ b/NEWS @@ -4,6 +4,11 @@ Version 1.11.2 (RGer), 2005-10-20 by an alarm handler, which could lead to all sorts of bad things. This has been changed now. See comments in syslogd.c/domark() for details. - improved debug output for property-based filters +- not a code change, but: I have checked all exit()s to make sure that + none occurs once rsyslogd has started up. Even in unusual conditions + (like low-memory conditions) rsyslogd somehow remains active. Of course, + it might loose a message or two, but at least it does not abort and it + can also recover when the condition no longer persist. --------------------------------------------------------------------------- Version 1.11.1 (RGer), 2005-10-19 - support for BSD-style program name and host blocks -- cgit