init: needs a way to define startup priorities
Upstart needs some clear way to define whether jobs should start early or late, and before or after another job in the boot process. To put it short it needs a priority value for jobs like the old ordering of startup scripts by name.
For a fast startup on desktop systems I want all desktop related jobs to start before server jobs. Currently, there seems to be no easy way to achieve this. Jobs with little event dependencies for startup simply come first which is ok for server systems, but not for desktop systems.
E.g. mythtv-backend comes with a startup script that only depends on local-filesystems so it gets started very early which is not desirable for desktop systems. It should startup only after gdm (and user session) have finished loading. i.e. all jobs need a priority field to put them early or late in the boot while respecting event dependencies.
And second: when do upstart jobs get started in respect to legacy init.d scripts which have not been converted, yet? I wonder how I can force mysql server, for example, to start up later in the boot process.
|Changed in upstart:|
|status:||New → Triaged|
|importance:||Undecided → Wishlist|
- upstart needs a way to define startup priorities
+ init: needs a way to define startup priorities