Without having to manually trace dependencies, e.g. with
systemctl show or
systemctl cat, and manually inspect the state of the system with
systemctl status and
systemctl list-units, is there a way to preview what a
systemctl stop|start|restart would do?
Failing that, after the fact, is there a way to show a trace of which jobs were queued and why?
The kind of trace I would like to see in either case is something like:
starting X due to user request adding Y to the transaction because it is required by X adding Z1, Z2, Z3 because they are wanted by Y …
--dry-run option is only available on later versions of systemd than the one I have, and is documented to only be supported on certain operations that are not relevant for my use case.