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 you enter the emergency shell, check the journal if
systemd-journald.service has been stopped (and started again)
- If any of the above sockets are active?
they're all active...
systemd-journald.socket
systemd-journald-dev-log.socket, and
systemd-audit.socket
while in emergency..
I can only report against the latest two versions of systemd to github
upstream.
was told so, over here,
https://github.com/systemd/systemd/issues/21370
I tried to report upstream as much as possible in general, but with the
systemd project --- the upstream requires very recent builds --- which
debian doesn't have any... so I can't report my bugs upstream at that
location.
instead I am told by their lead developer to file things over here.
I also would like that other issue(I pasted url above), to be fixed as
well... are you going to tell me to report that upstream as well?
Mister Lennard Poettering is blaming broken debian md-raid packages ---
which is 100% not true at all.. it's just that he doesn't want to bother
for "older" systemd builds... I am 100% sure he could of looked more
into it, but he doesn't want to..
so fix it please.
FIX IT NOW!!!!!!
THANKS!!!!!
