Blueprint changed by Colin Watson: Whiteboard changed: Status: spec drafting, work items are still in flux Work Items: - [cjwatson] turn off quiet for server: TODO + [cjwatson] turn off quiet for server: DONE [jamesodhunt] allow upstart visualization tool to filter out jobs/events that aren't in existence: TODO [clint-fewbar] define/document a simple job/alias/event for "networking up", for generic network services: TODO define/document a simple job/alias/event for "system has booted", for /etc/rc.local type behavior: TODO improve start on for cron and other services (start when all user info available): TODO update Upstart Cookbook with "abstract jobs" and full exposition of how to define optimal "start on" and "stop on" for a new job: TODO [clint-fewbar] file bugs on services that don't respect single user mode appropriately: TODO [clint-fewbar] automated testing for single to multiuser: TODO [clint-fewbar] add init-checkconf rule to lintian for upstart jobs: TODO need to measure boot speed difference between sourcing /etc/default files, and not: TODO N/A work: define/document a simple job/alias/event for "local filesystems are up", for local services -- already exists, local-filesystems define/document a simple job/alias/event for "network filesystems are up", for network filesystem services - already exists, remote-filesystems Ideas * Serialize for debugging * Logging of job output (ideas also in upstart bug list) * Fencing (well defined sync points for boot) http://upstart.at/wp-content/uploads/2011/03/initctl2dot.png * as late as possible -- grub common one example for init.d * Generic Jobs (network-services, etc) * Document best practice in /usr/share/doc/upstart/examples and man page * Delay until all network interfaces are up * Default to always showing plymouth upstart bridge output * runlevel 1 and back to 2 doesn't work right * useful for emergency maintenance recovery * consider adding call to init-checkconf to lintian rule to ensure job config syntactically valid * clean-up behaviour of single-user mode * /etc/default/* -> what to do Actions:
-- Server boot experience https://blueprints.launchpad.net/ubuntu/+spec/server-o-boot-experience -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs