[systemd-devel] Service fails to start with no log messages

[Reindl Harald]

Am 07.01.20 um 02:57 schrieb Jeffrey Walton:
> To fix my ordering problem I need Systemd to stop lying about when the
> network is ready.

one last comment:

whatever crap you did ending in the ordering cycle did not solve your
wrong ordering after network, it just burried it by slow down something
else and so by luck

systemd does not lie here - you just need to do the ordering proper
based on how your network is configured at all which you refuse to tell

so your better options would have been report thate network ordering
problem here before touch anything else

"There are absolutely 0 entires about my monitor service" is because
it's thrown out of the startup transaction cause dby your other config
screwup