Comment by blibble

> Seems like you have an axe to grind with systemd because it replaced your familiar (but extremely cruddy) init system and now you refuse to debug the problem because you prefer being able to blame systemd.

I'm a pragmatist: I just want it to work

my solution to MULTIPLE different services failing to IP bind is to turn on the non-local ip binding sysctl, bypassing systemd's brokenness entirely

> There is so much granularity and flexibility in what you can do it seems rather unlikely you cannot make it happen correctly.

I've written an init before (in C), I know how the netlink interface to set an IP address and add routing table entries works

I understand the difference between monotonic and wall clocks

I understand the difference between Wants and Require

I know what's going on at every, single, level

and I can't stand how unreliable systemd makes nearly every single one of my, bluntly, completely vanilla systems

> And if it is truly a bug... open an issue?

did you read the link I pasted earlier?

I'm not wasting my time with that level of idiocy (from LP himself)