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

[Lennart Poettering]

On Mo, 06.01.20 21:47, Jeffrey Walton (noloader at gmail.com) wrote:

> On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald <h.reindl at thelounge.net> wrote:
> >
> > 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
>
> And there we have it. Systemd is not logging the problem. And then you
> wonder why users like me go down rabbit holes.
>
> Perhaps Systemd should hire someone who understands usability and
> design. Maybe they can explain why throwing important information away
> is a bad idea.

Not helpful at all. Consider both of you warned. One more post like
this and you are moderated.

Lennart

--
Lennart Poettering, Berlin