It's one thing to draw a line in the sand and say debian isn't going to allow any forking daemons... going forward. They are allowed now under initscripts, right? So that's an interesting bit of backward compatibility drama the project is going to go through..convincing maintainers to change from forking to non-forking across the board.
But that doesn't say anything about whether upstart actually WORKS as designed. Your just paper over one problem with in upstart at best via a policy fight. It can still lose track of running services via problems parsing the embedded start/stop scriptlets that upstart jobs allow. Is deb going to also disallow those scriplets to workaround upstart's design flaws? Good luck with that.
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds