| |||||||||||||
A licensing change for syslog-ngA licensing change for syslog-ngPosted Sep 10, 2010 7:50 UTC (Fri) by nix (subscriber, #2304)In reply to: A licensing change for syslog-ng by johoho Parent article: A licensing change for syslog-ng
we did not loose a single logline sinceI'm another happy syslog-ng user (the database and parser support *rock*, who needs separate log analysis programs anyway?) but I find myself wondering... if unimportant log lines were silently vanishing in transit, how would you know? :)
(Log in to post comments)
A licensing change for syslog-ng Posted Sep 10, 2010 8:41 UTC (Fri) by johoho (subscriber, #2773) [Link]
Initally we were using standard syslog daemon for local and remote logging. Over time we had some network trouble and were forced to re-transmit loglines to central logging server. Since we store all logs for 30 days local, this was not a problem. This local log was used to compare lines on the CLS with the local copies. If line count does not match, you have a problem.
PS: oh yes, rsyslog had trouble with remote / local loglines not being identical..
|
|||||||||||||