On Sat, 15 Nov 2014 07:04:03 +0200, Alan McKinnon wrote: > > [U] app-admin/syslog-ng > > Available versions: 3.4.7^t 3.4.8^t (~)3.5.6t,^t{tbz2}[1] > > (~)3.6.1^t{tbz2} {amqp caps dbi geoip ipv6 json mongodb pacct +pcre > > redis smtp spoof-source ssl systemd tcpd} > > Installed versions: 3.5.6^t{tbz2}[1](05:21:52 PM > > 11/14/2014)(ipv6 json pcre ssl systemd tcpd -amqp -caps -dbi -geoip > > -mongodb -pacct - smtp -spoof-source) > > Homepage: http://www.balabit.com/network-security/ > > syslog-ng > > Description: syslog replacement with advanced filtering > > features > > I don't find any info on what the syslog-ng ebuild does with > USE=systemd, I suspect it may want to use the fancy logging features > built into systemd.
Looking at the ebuild and ./configure --help output, it seems to be used to install service files and to change the restart command used by logrotate, which would cause you a problem later if you did actually get it working properly. There's also a configure option to use the journal, which may be the source of the problem. > Since you have it, but don't run it, does USE=-systemd fix the issue? Worth a try. If it does fix it I would consider it a bug since adding systemd support should not implicitly disable it under openrc. -- Neil Bothwick Windows Error #02: Multitasking attempted. System confused.
pgpIeaDwpKpNX.pgp
Description: OpenPGP digital signature