[syslog-ng] Systemd troubles: incompatibility with journald ?

[Balazs Scheidler]

please note that the persist file should be persisted accross reboots. but you probably know this anyway.

----- Original message -----
> Guillaume Rousse <guillomovitch at gmail.com> writes:
> 
> > Hello list.
> > 
> > I'm unable to run syslog-ng, whatever the version (I tried 3.3.6 and 
> > 3.4.1), on a recent system using systemd (mageia cauldron 64 bits, 
> > systemd 195). As soon as I'm launching syslog-ng, systemd and 
> > systemd-journal cpu usages reach 80/95%, and systemd fill dmesg log
> > with   this kind of message:
> > [ 5962.484250] systemd[1]: syslog-ng.service start request repeated
> > too   quickly, refusing to start
> 
> As it was found in the bug report too, the problem was due to the
> missing /var/syslog-ng directory. A similar problem was also recently
> reported in Debian:
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699942
> 
> The Debian report has the better fix, I believe. But indeed, this is a
> packaging error, but one that should be documented, and one that can be
> worked around with a change to the syslog-ng unit file.
> 
> I'll probably update the syslog-ng unit file, and/or write some
> documentation regarding syslog-ng and systemd, aimed at packagers.
> 
> -- 
> |8]
> 
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng FAQ:
> http://www.balabit.com/wiki/syslog-ng-faq
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20130208/d6bfdde2/attachment.htm