Bugzilla – Bug 1143144
Leap should save journalctl log since the begin - not only the current boot
Last modified: 2021-11-03 20:46:35 UTC
Because like how it work now by default, is not useful if you get a freeze or something
using this, you can fix this https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.journalctl.html#sec.journalctl.persistent
but this should be fixed by default
Ludwig, something that should be considered IMHO.
Please have a look.
The log is forwarded to rsyslog - and ends in /var/log/messages, duplicating this in the journal is just waste.
If you want persistant journal, install systemd-logger (which is the default on Tumbleweed btw, but Leap follows SLE's default of using rsyslog)
The documentation doesn't mention that option as SLE doesn't even ship systemd-logger
@Stephan, the point is to have the default changed and to rely on persistent journal only by default.
The need for rsyslog seems to exist only for a few server specific cases it seems and its need for a desktop distro, such as Leap, is very unlikely.
Even for SLE, the default is questionable IMHO.
I don't think Leap is a desktop distro. I for one use Tumbleweed on desktop, Leap on servers.
Leap is a distro for desktop users too
Tumbleweed = rolling release
Leap = stable
Leap is like ubuntu LTS
so yes, leap is for desktop/workstation/servers
I've forwarded the request to SLE PM (reference PM-1300). For TW I filed a sr for patterns-base.
This is an autogenerated message for OBS integration:
This bug (1143144) was mentioned in
https://build.opensuse.org/request/show/723306 Factory / patterns-base