Well, under systemd single-user mode is just a name of a target and nothing
special in itself.
I suppose the right thing would be figuring out not whether dbus is running or
not currently, but whether it *should* be running or not. If it's not even
supposed to be running in the current target then we have no business
complaining.
How to get that out of systemd I don't know. I would've thought 'systemctl
is-enabled dbus' would know, but booting (Fedora rawhide) to single user, it
says dbus is enabled yet the service is not running, it's just dead. I thought
this was just the kind of distinction that systemd was supposed to be able to
make... I also don't see any obvious way to determine what the current target
is, and whether a given service should be running in it or not.
I dunno. It's possible the code here is the best approximation we can
reasonably get. But in that case the commit message is a bit off, it should
describe what what it does, single user mode being just an example of a
situation where it would occur.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/831#issuecomment-529932761
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
