Sadly simple containers with little real world units seem to
avoid the problems. But I'm sure there will be some kind of fix for this
over the next week or so.
But my example doesn't have any units at all :-). I issue
two disable commands in a row for units that don't even
exist. I have no
Does systemd have any tests for malicious behavior?
People sending bazillions of dbus requests? People
sending random nonsense dbus requests? I'm just asking
because you gotta know someone is gonna do it if you
don't do it first :-).
I also find that merely sending two systemctl
disable commands
There doesn't appear to be any way to convince systemd
to abandon utterly unimportant stop jobs during
shutdown and advance to actually important things
like cleanly syncing and un-mounting local hard
disks.
For example, there are bugs like this:
However, something like that can never be the default, we need to give
services the chance to shut down cleanly and in the right order.
I didn't ask for any change to any default, I just asked for
users to be able to make the shutdown process proceed when
they have more information than systemd
