>I'm not saying systemd is the best answer, but I really think >sysadmins could learn a thing or two from developers.
>Nearly every custom init script I've ever seen has bugs, and >isn't portable between systems.
Nearly every custom init script is written by a developer for the product you desperately have to run because development wanted it, not bothering to give us sys admins time to look into the: packaging, configurability, operability and if a custom module/cookbook/playbook needs to be written.
>Where are the unit tests? Code reuse? >Focus on maintainability/readability?
If we were given the time, it would be there. My deadline for almost all work I do is "yesterday".
>Nearly every custom init script I've ever seen has bugs, and >isn't portable between systems.
Nearly every custom init script is written by a developer for the product you desperately have to run because development wanted it, not bothering to give us sys admins time to look into the: packaging, configurability, operability and if a custom module/cookbook/playbook needs to be written.
>Where are the unit tests? Code reuse? >Focus on maintainability/readability?
If we were given the time, it would be there. My deadline for almost all work I do is "yesterday".