On 22 February 2018 at 21:11, Bryan Quigley <bryan.quig...@canonical.com> wrote: > @markstos > Sorry, yea, I meant our defaults, not the journal config options itself. > SystemMaxUse= is unset in the config in bionic (although it's all commented > out, but I believe that's supposed to indicate our defaults?) > > Re:disk writing. I don't disagree, but if we are SRUing it we need to > consider that more. For 18.04 we can still decide to remove rsyslog to > reduce the impact, we can't do that for 17.10/16.04. >
Current situation of non-persistent logs imho is critical bug. It has a severe impact, data loss, on a large portion of Ubuntu users. To reduce duplication, one of the suggestions was to still forward messages to rsyslog (for forwarding) but do not store those that are coming from journald on disk, as journald already has them one disk. Alternative, is to switch to syslog-ng with journald module such that it pulls in rich journal messages into syslog, and make journald stop forwarding messages to syslog. Another alternative is to drop rsyslog from default install, and make journald be the default syslog provider on Ubuntu. I am undecided on how to best implement de-duplication of a portion of messages in Ubuntu going forward, but above are three technically plausible paths to solve this. -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
