Originally posted by tinko
View Post
Ok... I know, you systemd guys are thinking "we are right" (can they think any other way?)... and therefore it's a puppet problem. I'm just pointing out that systemd (to use systemd speak) "has exposed many problems in other peoples software". And we, the sysadmins and devops of the world, have to pay the price. I know that all systemd proponents have convered their ears at this point... I fully understand it's my problem to contend with, but to say "it isn't because of systemd" is just incorrect. It's just life and life got a whole lot more painful during this transition.
I am glad you haven't seen the lockup on shutdown... if you ever do see this, will you be honest enough to post? Just because I'm not afraid to point systemd failings doesn't make me your enemy. Or does it?
Again, these are full lockups, so difficult to diagnose (especially with systemd...sorry, but must be said).
Comment