Bug#950447: Document that persistent journal is now enabled in systemd
Andrei POPESCU wrote > On Mi, 31 mar 21, 17:33:47, Justin B Rye wrote: >> + >> + Persistent systemd journal >> + >> +Systemd in bullseye activates its persistent journal functionality >> +by default, storing its files in >> +/var/log/journal/. See > + >> url="/bullseye/systemd/journald.conf.5.html">journald.conf(5) >> +for details. > > To me systemd-journald.service(8) seems like a better introduction. And it does have a fairly conspicuous pointer towards journald.conf(5) and Storage= in particular. Fair enough. > It's probably also worth mentioning that on Debian the journal is > readable by members of 'adm', in addition to the default > 'systemd-journal' group. So something like the attached: -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package diff --git a/en/whats-new.dbk b/en/whats-new.dbk index 1e361e61..c271945c 100644 --- a/en/whats-new.dbk +++ b/en/whats-new.dbk @@ -182,6 +182,25 @@ linkend="obsolete"/>. + + Persistent systemd journal + +Systemd in bullseye activates its persistent journal functionality +by default, storing its files in +/var/log/journal/. See systemd-journald.service(8) +for details; note that on Debian the journal is readable for +members of adm, in addition to the default +systemd-journal group. + + +This should not interfere with any existing traditional logging +daemon such as rsyslog, but +users who are not relying on special features of such a daemon may +wish to uninstall it and switch over to using only the journal. + + + Desktops and well known packages
Bug#950447: Document that persistent journal is now enabled in systemd
On Mi, 31 mar 21, 17:33:47, Justin B Rye wrote: > Paul Gevers wrote: > >> On 18-03-2021 11:41, Michael Biebl wrote: > >>> Yes, the persistent journal is enabled on upgrades and new installations. > >> > >> Thanks. > >> > >>> I'm a bit uncertain, whether I should go into that much detail in the > >>> release notes, especially wrt to rsyslog. But on the other hand, this > >>> way our users are notified in advance that this change is coming. > >> > >> I would say, keep it short. I.e. tell we change the default (it only the > >> default, right?) on upgrades and how it can be disabled again. > > > > Did you already have inspiration? We can also try to write up something, > > but I really appreciate it when maintainers do the initial proposal. > > If nobody knowledgeable has had the time to come up with anything, > maybe the version attached will inspire either improvements or just an > urge to replace it with something completely different. > > (The man page pointer should be enough that we don't also need to > spell out a "disabling the journal HOWTO".) > diff --git a/en/whats-new.dbk b/en/whats-new.dbk > index 1e361e61..399e1977 100644 > --- a/en/whats-new.dbk > +++ b/en/whats-new.dbk > @@ -182,6 +182,23 @@ linkend="obsolete"/>. > > > > + > + Persistent systemd journal > + > +Systemd in bullseye activates its persistent journal functionality > +by default, storing its files in > +/var/log/journal/. See + > url="/bullseye/systemd/journald.conf.5.html">journald.conf(5) > +for details. To me systemd-journald.service(8) seems like a better introduction. It's probably also worth mentioning that on Debian the journal is readable by members of 'adm', in addition to the default 'systemd-journal' group. > + > + > +This should not interfere with any existing traditional logging > +daemon such as rsyslog, but > +users who are not relying on special features of such a daemon may > +wish to uninstall it and switch over to using only the journal. > + > + > + > >Desktops and well known packages > Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Bug#950447: Document that persistent journal is now enabled in systemd
Paul Gevers wrote: >> On 18-03-2021 11:41, Michael Biebl wrote: >>> Yes, the persistent journal is enabled on upgrades and new installations. >> >> Thanks. >> >>> I'm a bit uncertain, whether I should go into that much detail in the >>> release notes, especially wrt to rsyslog. But on the other hand, this >>> way our users are notified in advance that this change is coming. >> >> I would say, keep it short. I.e. tell we change the default (it only the >> default, right?) on upgrades and how it can be disabled again. > > Did you already have inspiration? We can also try to write up something, > but I really appreciate it when maintainers do the initial proposal. If nobody knowledgeable has had the time to come up with anything, maybe the version attached will inspire either improvements or just an urge to replace it with something completely different. (The man page pointer should be enough that we don't also need to spell out a "disabling the journal HOWTO".) -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package diff --git a/en/whats-new.dbk b/en/whats-new.dbk index 1e361e61..399e1977 100644 --- a/en/whats-new.dbk +++ b/en/whats-new.dbk @@ -182,6 +182,23 @@ linkend="obsolete"/>. + + Persistent systemd journal + +Systemd in bullseye activates its persistent journal functionality +by default, storing its files in +/var/log/journal/. See journald.conf(5) +for details. + + +This should not interfere with any existing traditional logging +daemon such as rsyslog, but +users who are not relying on special features of such a daemon may +wish to uninstall it and switch over to using only the journal. + + + Desktops and well known packages
Bug#950447: Document that persistent journal is now enabled in systemd
Hi Michael, On 18-03-2021 12:04, Paul Gevers wrote: > On 18-03-2021 11:41, Michael Biebl wrote: >> Yes, the persistent journal is enabled on upgrades and new installations. > > Thanks. > >> I'm a bit uncertain, whether I should go into that much detail in the >> release notes, especially wrt to rsyslog. But on the other hand, this >> way our users are notified in advance that this change is coming. > > I would say, keep it short. I.e. tell we change the default (it only the > default, right?) on upgrades and how it can be disabled again. Did you already have inspiration? We can also try to write up something, but I really appreciate it when maintainers do the initial proposal. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#950447: Document that persistent journal is now enabled in systemd
Control: tags -1 - moreinfo Hi Michael, On 18-03-2021 11:41, Michael Biebl wrote: > Yes, the persistent journal is enabled on upgrades and new installations. Thanks. > I'm a bit uncertain, whether I should go into that much detail in the > release notes, especially wrt to rsyslog. But on the other hand, this > way our users are notified in advance that this change is coming. I would say, keep it short. I.e. tell we change the default (it only the default, right?) on upgrades and how it can be disabled again. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#950447: Document that persistent journal is now enabled in systemd
Hi Paul Am 18.03.2021 um 11:29 schrieb Paul Gevers: Control: tags -1 moreinfo HI Michael, On Sat, 01 Feb 2020 21:45:06 +0100 Michael Biebl wrote: See https://lists.debian.org/debian-devel/2020/02/msg4.html We should document in the release notes, that systemd has enabled persistent logging in journald. Personally, I would prefer to do that on upgrades and new installations and document that accordingly (and that is what the systemd package currently does). The discussions on debian-devel are still ongoing, so this might still change though. So, what's the end status in bullseye now? Can you propose a text? Yes, the persistent journal is enabled on upgrades and new installations. What I didn't push for is the demotion of rsyslog from important to optional, so rsyslog is still installed by default as well. I plan to change that in bullseye+1 (*) This is sort of deliberate to have both installed for one release cycle. Just in case something goes horribly wrong with the persistent journal (which I don't expect), users still have their known plaintext log files as fallback. I'm a bit uncertain, whether I should go into that much detail in the release notes, especially wrt to rsyslog. But on the other hand, this way our users are notified in advance that this change is coming. Paul, wdyt? (*) My plan would be, to simply demote rsyslog to optional, but not actively remove it on upgrades. OpenPGP_signature Description: OpenPGP digital signature
Bug#950447: Document that persistent journal is now enabled in systemd
Control: tags -1 moreinfo HI Michael, On Sat, 01 Feb 2020 21:45:06 +0100 Michael Biebl wrote: > See > https://lists.debian.org/debian-devel/2020/02/msg4.html > > We should document in the release notes, that systemd has enabled > persistent logging in journald. > Personally, I would prefer to do that on upgrades and new installations > and document that accordingly (and that is what the systemd package > currently does). > > The discussions on debian-devel are still ongoing, so this might still > change though. So, what's the end status in bullseye now? Can you propose a text? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#950447: Document that persistent journal is now enabled in systemd
Package: release-notes Severity: normal See https://lists.debian.org/debian-devel/2020/02/msg4.html We should document in the release notes, that systemd has enabled persistent logging in journald. Personally, I would prefer to do that on upgrades and new installations and document that accordingly (and that is what the systemd package currently does). The discussions on debian-devel are still ongoing, so this might still change though. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
