| |||||||||||||
I'm still confused...I'm still confused...Posted Dec 11, 2011 17:54 UTC (Sun) by jrn (subscriber, #64214)In reply to: I'm still confused... by raven667 Parent article: Distribution quote of the week
> This doesnt have anything to do with systemd trying to eat your baby, It just exposed more pre-existing cases that were broken in the current setup
Did systemd actually provoke any worse behavior? I had assumed it was just warning about this class of bugs for kicks.
(Log in to post comments)
I'm still confused... Posted Dec 12, 2011 4:08 UTC (Mon) by raven667 (subscriber, #5198) [Link]
Systemd starts services as needed which probably created several service start orders that, while perfectly valid, hadnt been tested in practice and broke.
|
|||||||||||||