* Anton Aylward <opensuse@antonaylward.com> [08-24-16 09:04]:
On 08/24/2016 02:20 AM, Felix Miata wrote:
On some installations (e.g. TW/KDE3 host hpg33), there's no sign of anything like it in journalctl, in fact, nothing from journalctl ever shows up anywhere in /var/log/,
I seem to recall reading here some while ago and thence setting my system so that journalctl is echoed to syslog, or at least the rsyslog that I use, and hence *also* comes out consuming duplicate disk space in /var/log.
I don't feel like searching the archives for that this am, other demands on my time, but perhaps that gives a clue as to what for look for -- a configuration option.
You say "on some...". What about others? How different is the syslog/systemd/journalctl configuration between them?
[r]syslogd is not installed unless specified as the system defaults to systemd-journald. w/o [r]syslog there is no logging to /var/log, from "man systemd-journald": By default, the journal stores log data in /run/log/journal/. Since /run/ is volatile, log data is lost at reboot. To make the data persistent, it is sufficient to create /var/log/journal/ where systemd-journald will then store the data: mkdir -p /var/log/journal systemd-tmpfiles --create --prefix /var/log/journal systemd-journald will forward all received log messages to the AF_UNIX/SOCK_DGRAM socket /run/systemd/journal/syslog, if it exists, which may be used by Unix syslog daemons to process the data further. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org