Public bug reported:
Binary package hint: upstart
This upstart configuration file worked in Karmic:
# hvc0.conf
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -8 38400 hvc0
After the upgrade to Lucid, something is silently moving this file to
/etc/event.disabled and not logging the action.
If I move this file back to /etc/init and do `initctl start hvc0`, then
the getty is properly started. It is only at boot time that the upstart
fails to start the getty.
I tried these variants:
# hvc0.conf
start on tty-added
stop on tty-removed TTY=$TTY
instance TTY
exec /sbin/getty -8 38400 $TTY
# hvc0.conf
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -8 38400 hvc0
# hvc0.conf
start on (tty-device-added KERNEL=hvc0 and runlevel [23])
exec /sbin/getty -8 38400 hvc0
In the Xen guest domU environment, these configurations all work for tty
console devices, but not for hvc console devices during system startup.
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
