** Description changed: systemd journald configuration in /usr/lib/systemd/journald.conf.d/syslog.conf enforces duplication of the logs into rsyslog with: ForwardToSyslog=yes $ cat /usr/lib/systemd/journald.conf.d/syslog.conf # Undo upstream commit 46b131574fdd7d77 for now. For details see # http://lists.freedesktop.org/archives/systemd-devel/2014-November/025550.html [Journal] ForwardToSyslog=yes journald has limits it can enforce, preventing disk-full issues, while rsyslog does not discriminate and just logs everything. The expectation that journald has limits is well-known in the community - and folks will activate trace log level in their snaps (for example) - without considering it could lead to logs filling the free disk space in - the underlying system. + and folks will activate trace log level in their snaps (for example + https://github.com/canonical/k8sd/issues/31) without considering it + could lead to logs filling the free disk space in the underlying system. Thank you!
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2147513 Title: Stop duplicating logs into Rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2147513/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
