6 ms·
> Numerous cases of that. Like when? Because I have interacted with projects where Lennart is part of the admin team and from where I stand it’s all in your he
by WastingMyTime89 4y ago
> Numerous cases of that.
Like when? Because I have interacted with projects where Lennart is part of the admin team and from where I stand it’s all in your head.
Both bugs and security are taken seriously.
> The above doesn't represent my personal opinion, it's a representation of what reasons people might have.
I admire the courage you display in standing for your opinion.
- labawi 4y agoI don't know about your experiences, but systemd is leaking preconceived notions and self-imposed limitations like a broken sieve where one is left to sift manually through documentation and bug-reports, collecting and evaluating rules, exceptions and idiosyncratic notions to determine whether systemd will do what one wants. Latest example: I have a service I want running, so I set it to Restart=always. Read the long Restart= documentations - seems ok. Does it work? Failure 1: Well.. you also need appropriate RestartSec/StartLimitInterval. Ok, I I set it up. Does it work? Failure 2: Well.. restart doesn't actually apply to failed dependencies, so .. don't have dependencies that fail, ok? That's not a bug. [1][2] [1] https://github.com/systemd/systemd/issues/1312 https://github.com/systemd/systemd/issues/1312 [2] https://unix.stackexchange.com/questions/213185/restarting-systemd-service-on-dependency-failure https://unix.stackexchange.com/questions/213185/restarting-s...