upstart job locks up switching from single user mode back to runlevel 2
Bug #756787 reported by
Clint Byrum
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| drizzle (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: drizzle
Since local-filesystems and net-device-up only happen during boot, using "and" with them and runlevel will mean that the runlevel event can never complete.
drizzle should just 'start on runlevel [2345]'
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in drizzle (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package drizzle - 2011.03.13-0ubuntu2
---------------
drizzle (2011.03.
* patches/
branch to enable --user option. (LP: #740583)
* drizzle.upstart: use --user option to set user to drizzle
(LP: #739778)
* drizzle.preinst: fix permissions on /var/lib/drizzle if user ran a
version prior to this and ran as root.
* drizzle.upstart: change start on to just start on runlevel [2345]
so that switching from single user to multi works (LP: #756787)
* conf.d/
* drizzle.upstart: pipe output to logger to catch plugin problems.
* drizzle-
random password using pwgen (added to deps in control).
-- Clint Byrum <email address hidden> Sun, 10 Apr 2011 22:44:30 -0700