https://bugzilla.balabit.com/show_bug.cgi?id=137 Summary: [debian #642479]: should print a warning at startup if not configured to log anything Product: syslog-ng Version: unspecified Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642479 OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: algernon@balabit.hu Type of the Report: --- Estimated Hours: 0.0 The following report was filed in the Debian BTS against the syslog-ng package: So I was frustrated for a while by why "/var/log/messages", etc., all had a timestamp of a few months ago (which is when I last installed or reconfigured Syslog-NG on this host). The attached file does work; I'm pretty sure the problem was that I had a whole page of "log(...)" statements with no "source(...)" option and no "catchall" flag. If the start-script can prove by static analysis that it's impossible for any messages to match and be written to any destination, it should print a warning, not just start silently. In fact, a "log(...)" statement with no "source(...)" option and no "catchall" flag should probably trigger a warning. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.