Apologies I didn't post this in the bug, but this was discussed before -
https://lists.ubuntu.com/archives/ubuntu-devel/2017-January/039634.html
(crosses -devel and devel-discuss)
My understanding was we were just waiting on implementation details (how
much/long to store in the journal, how to
I started a policy discussion on ubuntu-devel about whether systemd
journal logging should be persistent by default:
https://lists.ubuntu.com/archives/ubuntu-devel/2017-November/040031.html
I encourage to participate. Non-developers can still participant, but
posts will be moderated (that's how
In addition to Dimitri comments, my patch also would result in a much
larger journal then comparable rsyslog. I managed to get mine up to
multiple GBs which on a slow disk, appears to actually slow down
logging.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Let's give this discussion another dimension. Non-persistent logging as
default made it impossible to debug a critical `fwupdate` bug where the
OS doesn't boot after a firmware update:
https://github.com/rhboot/fwupdate/issues/86
Please, please, just enable persistent logging by default. Systemd
@olberd: Yes, I as a "typical user" can confirm that. I just wanted to
get some log data from the previous boot and was really surprised to
find that only the current boot was available. I have changed the
setting now, but the data I wanted is lost forever.
--
You received this bug notification
@dino99: I think the typical user won't realize, that the logs are being
thrown away, until they need a log from the previous boot. By then it is
too late to correct the configuration.
Why not set `Storage=persistent` in `/etc/systemd/journald.conf` instead
of creating the folder. That would
According to systemd-journald's man page, this should do it:
mkdir -p /var/log/journal
systemd-tmpfiles --create --prefix /var/log/journal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618188
@dino99. Because good defaults matter. Being safe by default is
important. Being secure by default is important.
The "Principle of least surprise" applies here:
"In general engineering design contexts, the principle can be taken to
mean that a component of a system should behave in a manner
@All
not a big deal to create /var/log/journal if a user want/need it; its
documented since the beginning. So why doing things complicated when the
actual default is light enough ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@bryanquigley
I agree that this should be done; however that trivial patch is not
quite enough, as one has to make sure the permissions on the directory
are correct and that one allows disabling that feature too, and preserve
the admin choice w.r.t. that on upgrades, and we do need flush the
@dino99 how was "what most users prefer" prefer determined? Was there a
poll?
Systemd already has configuration options to limit the growth the the
journal. As documented in `man journald.conf`, the defaults are already
set to prevent filling up a disk.
If there were a poll, I can certainly
Given the discussions on ubuntu-devel/discuss, the controversial part
seemed to be more around removing rsyslog, and we haven't gotten (or I
haven't seen) any pushback on just doing both for now.
dino99>the actual 'non permanent' journal by default is that most users prefer;
Why do you believe
Trivial patch that just ensures the /var/log/journal directory gets
created.
** Patch added: "systemd_232-17ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+attachment/4818279/+files/systemd_232-17ubuntu2.debdiff
--
You received this bug notification because
Everyone can set a permanent storage:
sudo mkdir -p /var/log/journal
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-
to-view-and-manipulate-systemd-logs
http://unix.stackexchange.com/questions/191313/why-is-my-systemd-
journal-not-persistent-across-reboots
--
You
Comment:
the actual 'non permanent' journal by default is that most users prefer;
and should continue to be to avoid fullfilling the storage device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I actually don't mind the "logging everything twice" bit. As journald
has good garbage collection built in, and has much better timestamps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618188
I understand it is not desirable to have duplicate logging, but there is
a corner case where logging that is done during systemd shutdown is lost
because rsyslog is killed. This makes shutdown look broken due to it
being non-deterministic exactly when rsyslog is killed.
Currently, the easiest way
17 matches
Mail list logo
