Public bug reported:
Binary package hint: upstart
doing some comparisons this morning for different runlevels in ubuntu
7.10 I found that changing to some runlevels from within a running
system (gnome-terminal inside ubuntu desktop) does not function as
expected. I understand that upstart does not have a notion of
traditional runlevels, but tries to retain some compatibility with them.
the errors below seem to be bugs in regards to this compatibility. In
additional testing it appears that switching to single user mode via s,S
is not something that a user would want. If it is to be avoided, and if
it causes the errors as below, I would argue it should be removed from
the valid options of the [tel]init command.
sudo init s - causes respawn prompts within the shell nearly infinitely. the
machine must be powered down
sudo init S - causes keyboard input problems. different result than above, but
machine must also be powered down
sudo init singe - complains about invalid option to init, despite single being
valid from grub
init --help does not list the valid options for use with init
man init does not list valid options for use with init either
sudo telinit s - similar problem to 'init S' above. required power down of
machine.
sudo telinit S - same issue as above
sudo init 0 and sudo init 6 function as expected
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
[7.10] [tel]init [s,S] does not function as expected - locks the machine
https://bugs.launchpad.net/bugs/164134
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
