On Tue, Apr 1, 2008 at 10:57 AM, Balazs Scheidler <bazsi@balabit.hu> wrote:
It was integrated in syslog-ng OSE 2.1, as announced earlier I only fix really critical issues in 2.0, it is in strict maintenance mode. I'd rather like to get more testing for syslog-ng OSE 2.1.
The patch itself can be backported easily, here's the patch:
Great! Thanks a lot ... I'll give it a try. Regards, Andreas
http://git.balabit.hu/?p=bazsi/syslog-ng-2.1.git;a=commitdiff;h=39e54c9b7ad7...
On Tue, 2008-04-01 at 10:03 +0200, Andreas Kurz wrote:
Hello!
I am using syslog-ng 2.0.8 (and tested 2.0.9 to see if it includes the feature...) and found out that there is still no cmdline option to define the path/name of the "syslog-ng.persist" file (like for the pid/conf file). So it is not possible to easy run several Instances of syslog-ng using the file source driver on the same machine and store the file positions beyond syslog-ng restarts ... e.g. in a cluster environment .... or did I miss a hidden config option?
There was already a discussion about this some months ago. Is there a special reason, why this feature is not integrated in syslog-ng or is there only too less demand for such a feature?
-- Bazsi
______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.campin.net/syslog-ng/faq.html