From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] syslog-ng-3.6.1 nearly no log anymore
Date: Mon, 17 Nov 2014 07:59:57 -0500 [thread overview]
Message-ID: <CAGfcS_nLH0PtJ5mE1NULj1EuSb4DAhGtDGunixSGD+LuPF-aKg@mail.gmail.com> (raw)
In-Reply-To: <20141117104447.2e2070a3@digimed.co.uk>
On Mon, Nov 17, 2014 at 5:44 AM, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Mon, 17 Nov 2014 05:32:14 -0500, Tom H wrote:
>
>> Is the "systemd" USE flag an actual syslog-ng compilation option or it
>> is a flag to generate systemd units when syslog-ng is installed?
>
> Both.
>
Please read the ebuild before giving answers like this. The unit file
is installed regardless of flag setting (which is the standard
policy). There is a compile-time option which this also toggles, and
it also changes the logrotate script (which probably isn't ideal).
I don't know offhand what toggling the compile-time option does. It
seems that it does more than simply enable systemd support, though
there might be run-time options to control that and if so those should
be added to the openrc init.d script.
Looking at the syslog-ng admin guide, consider changing your log
source from system() (which autodetects the source) to something like:
unix-dgram("/dev/log");
file("/proc/kmsg" program-override("kernel") flags(kernel));
That appears to be what system() does when not running systemd. If
this works then I think upstream might accept a bug report on this -
the autodetection code isn't actually detecting whether systemd is
running, but whether it was enabled/installed/etc.
--
Rich
next prev parent reply other threads:[~2014-11-17 13:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 16:41 [gentoo-user] syslog-ng-3.6.1 nearly no log anymore Helmut Jarausch
2014-11-13 20:05 ` Alan McKinnon
2014-11-14 16:18 ` Helmut Jarausch
2014-11-14 17:46 ` Alan McKinnon
2014-11-14 18:44 ` Helmut Jarausch
2014-11-15 5:04 ` Alan McKinnon
2014-11-15 9:34 ` Neil Bothwick
2014-11-15 20:08 ` Walter Dnes
2014-11-15 21:11 ` Rich Freeman
2014-11-17 5:54 ` Walter Dnes
2014-11-17 10:32 ` Tom H
2014-11-17 10:44 ` Neil Bothwick
2014-11-17 12:59 ` Rich Freeman [this message]
2014-11-17 13:12 ` Neil Bothwick
2014-11-15 22:42 ` Neil Bothwick
2014-11-14 19:26 ` Tanstaafl
2014-11-14 7:01 ` Tomas Mozes
2014-11-14 7:16 ` Tomas Mozes
2014-11-14 12:27 ` J. Roeleveld
2014-11-15 2:47 ` Stroller
2014-11-17 15:51 ` Helmut Jarausch
2014-11-17 18:55 ` Rich Freeman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGfcS_nLH0PtJ5mE1NULj1EuSb4DAhGtDGunixSGD+LuPF-aKg@mail.gmail.com \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox