Just to weigh in on this, I am seeing similar problems. It seems to have started with the upgrade to fedora fc18 and syslog-ng-3.3.8-1.fc18.i686. In my case I get the error constantly scrolled across ALL terminal screens at boot-up. The only way of getting control of the system back is to ssh in from another machine and killing syslog-ng. I have taken to disabling syslog-ng (and enabling rsyslog) before reboots (which are thankfully seldom required) and then reversing that after the boot is complete. That seems to solve the problem, and syslog-ng stays up. -----Original Message----- From: Gergely Nagy [mailto:algernon@balabit.hu] Sent: Saturday, February 23, 2013 8:14 AM To: Syslog-ng users' and developers' mailing list Subject: Re: [syslog-ng] No "-n" switch for syslog-ng? Jakub Jankowski <shasta@toxcorp.com> writes:
On 2013-02-23, Gergely Nagy wrote:
I'm fairly sure this is an issue with one of the unit files. But if it turns out that systemd does add an implicit -n under some circumstances, then syslog-ng should support that, for compatibility's sake.
*If* systemd added an implicit -n somewhere, that would be an extremely stupid idea, and I really see no reason why apps should change just to accomodate such idiocy.
I'm quite sure it is not systemd itself, but in the off-chance it is, an alias of -n to -F is about one line. If it were more than that, I would be strongly against it too. But chances are, it's a rogue unit file somewhere. -- |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