Your message dated Mon, 4 Jul 2022 14:56:55 +0200
with message-id <2835e26f-1387-51c3-ce2c-334ccf62f...@debian.org>
and subject line Re: systemd: emergency/rescue targets fail to stop journald
has caused the Debian Bug report #999695,
regarding systemd: emergency target fails to stop journald
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
999695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 247.3
Severity: normal
"systemctl isolate emergency" fails to stop systemd-journald..
it's not an upstream issue since the problem does not occurr with other
distributions.
having systemd-journald to be stopped is desirable since the
administrator can then use e2fsck to repair filesystems(after the
problematic filesystem read-only -- "mount -o ro,remount /" for instance)
upstream won't look into this because it is not happening on other
distributions.
please take a look
thanks
--- End Message ---
--- Begin Message ---
On Sun, 14 Nov 2021 21:44:53 -0500 westlake <westlake2...@videotron.ca>
wrote:
However if the user boots normally into multi-user or graphical targets,
and types "systemctl isolate emergency" or "systemctl emergency", debian
does not stop systemd-journald services.
this is a problem noticeably if the user wants to perform work on "/"
with "mount -o ro,remount /".
I discussed this with upstream in the context of
https://github.com/systemd/systemd/pull/23863#issuecomment-1169866253
They rejected the idea of automatically stopping journald when entering
rescue mode. The correct way of making journald stop logging to /var
(and keeping /var or / busy), is to use `journalctl --relinquish-var` in
the case you want to fsck those file systems.
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
