On 2015-02-15 15:50:49, Leonid Isaev wrote:
TL:DR: Syslog-ng in [extra] is kind of broken, so you'll need to a few steps
to
get it to work in your environment.
1. (...)
2. (...)
3. (...)
4. (Re)enable syslog-ng.service and restart syslog.
A cookie, a mug of hot steaming morning drink
## vanilla /etc/syslog-ng/syslog-ng.conf
# grep -v '^#' /etc/systemd/journald.conf
[Journal]
Storage=none
ForwardToSyslog=no
ForwardToKMsg=no
ForwardToConsole=no
ForwardToWall=no
# note: ForwardToSyslog set to no as per the first few paragraphs of
# https://wiki.archlinux.org/index.php/syslog-ng
TL:DR: Syslog-ng in [extra] is kind of broken, so you'll need to a few steps to
get it to work in your environment.
On Sun, Feb 15, 2015 at 10:37:22AM +0100, ephae...@gmx.net wrote:
## vanilla /etc/syslog-ng/syslog-ng.conf
# grep -v '^#' /etc/systemd/journald.conf
[Journal]
On 2015-02-15 08:34:23, Troy Engel wrote:
On Sun, Feb 15, 2015 at 3:37 AM, ephae...@gmx.net wrote:
## vanilla /etc/syslog-ng/syslog-ng.conf
# grep -v '^#' /etc/systemd/journald.conf
It sounds like syslog-ng doesn't understand where the source is - (...)
In fact, you pointed me to the
4 matches
Mail list logo
