Hi,

There is a pull request on to 3.6/master:

https://github.com/balabit/syslog-ng/pull/327

I created it on morning, but it is not listed in the pull requests list

Viktor

On Thu, Dec 4, 2014 at 12:27 PM, Balazs Scheidler <bazsi77@gmail.com> wrote:

Hi,

Viktor could you pls share the fix for this? I know I promised to port it, but got distracted.

Thanks.

On Dec 4, 2014 11:36 AM, "LoneVVolf" <lonewolf@xs4all.nl> wrote:

On 04-12-14 09:58, Tibor Benke wrote:

I think you've found a bug in service-management.c:

https://github.com/balabit/syslog-ng/blob/master/lib/service-management.c#L158-L171

If you have syslog-ng compiled with --enable-systemd, it will always be the active service-management unit. I thought we addressed this in a patch by jviktor.

Tibor,

Is that code run during compiling/building or at run-time ?
Archlinux developers build packages on machines with an archlinux base installation with systemd installed & active .
If service-management.c is executed at build-time, that would explain why syslog-ng tries to use systemd on my system.

Given the multi-platform support of syslog-ng i would expect such checks to be executed at run-time .

2014-12-04 0:04 GMT+01:00 Balazs Scheidler <bazsi77@gmail.com>:

Also, you might want to use the system() source, which tries to determine the optimal setup to fetch local messages. So no need to use I unix-dgram or internal directly.

Balazs, thanks for the tip. After the problem is fixed, i'll look into using that.

______________________________________________________________________________
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