© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(I like the idea of upstart, so please don't consider this as bashing!)
I'd like to see this bug re-opened, because there's still not sufficient documentation and some aspects of upstart indicate that it may be immature for a LTS release (IMHO).
Some items I'd like to see addressed:
- a graphing tool to help debug upstart events/jobs
(a tool to process all related files, turning out a dot file so graphviz can make a pretty graph would be great)
- a tool showing (a graph of) the sequence of events and jobs perfomed by upstart until that moment since startup
- better documentation, in the form of a complete discussion/tutorial of the (ideal) upstart system
- an upstart tutorial for sysadmins who are used to sysV init scripts
One of the things that caused me to doubt the readiness for LTS is the lines in mountall(8):
This is a temporary tool...
...you should not rely on its behaviour.
Another is the strange mixing of SysV initscripts with upstart jobs, it's seriously confusing! Lack of proper documentation in this situation doesn't help.
I notice quite a few unanswered upstart discussions on the forum:
http://
http://
http://
are there so few people who can easily answer such queries?
If I were to run into trouble with upstart, where should I turn for help? it seems Canonical is one of the few places one can turn to for help, is this open source vendor lock-in?
Cheers
Simon