Am 28.11.21 um 12:37 schrieb westlake:
On 2021-11-15 10:10 a.m., Michael Biebl wrote:
I think, what you see is that systemd-journald.service *is* actually
stopped when you run `systemctl emergency`.
systemctl isolate emergency and systemctl emergency have the same
results unfortunately..
On 28.11.21 12:37, westlake wrote:
FIX IT NOW!!
Please dial down your rhetoric a couple of notches.
All it has achieved so far is that I'm no longer motivated to look at
this issue.
OpenPGP_signature
Description: OpenPGP digital signature
On 2021-11-15 10:10 a.m., Michael Biebl wrote:
I think, what you see is that systemd-journald.service *is* actually
stopped when you run `systemctl emergency`.
systemctl isolate emergency and systemctl emergency have the same
results unfortunately..
Could you check the following:
- When
Am 15.11.21 um 03:44 schrieb westlake:
Upon booting up with "systemd.unit=emergency.target" to the kernel
bootline, there are no systemd-journald services running.
I'd say this is expected, as sockets.target is not started. See below
However if the user boots normally into multi-user or
Package: systemd
Version: 247.3-6
Severity: normal
Upon booting up with "systemd.unit=emergency.target" to the kernel
bootline, there are no systemd-journald services running.
However if the user boots normally into multi-user or graphical targets,
and types "systemctl isolate emergency" or
5 matches
Mail list logo
