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