No, it will make no difference as it would not be running when the stop
event came in
--
Virtual Consoles still load at startup
https://launchpad.net/bugs/61539
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks Jayson. That definitely worked that time.
Last question.. what about commenting out the Stop line? Will that
theoretically speed up shutdown (even though it probably would not be
noticable)?
--
Virtual Consoles still load at startup
https://launchpad.net/bugs/61539
--
ubuntu-bugs mailin
Ah ok good to know. I fugred the respawn is only there to keep that VC
listening when a user exists that VC. But of course it can't respawn a
VC that never existed anyway, so I see why it's safe to leave 'respawn'
uncommented.
--
Virtual Consoles still load at startup
https://launchpad.net/bug
You don't need to comment out the respawn line, commenting out the
"start on" lines is sufficient
--
Virtual Consoles still load at startup
https://launchpad.net/bugs/61539
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ah ok. I left out an important step :) You must go into the directory
/etc/event.d/ and you will see files tty1 -> tt6. Edit all the tty
files that you do NOT want to be loaded on startup. Every line that
has a 'start' in front of it, comment that out. Also comment out the
'respawn' line at
Thanks for the info.
I do have that /etc/default/console-setup file, and I have changed the 6
to a 2, and I restarted.
Still seems to load up all 6 of the consoles.
--
Virtual Consoles still load at startup
https://launchpad.net/bugs/61539
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
Er let me correct myself. Knot 2 and below still used the old init
system, but since Knot3 was released (technically before...) upstart is
the init system. This does not use /etc/inittab.
** Changed in: Ubuntu
Sourcepackagename: None => upstart
Assignee: (unassigned) => Jayson Vaughn
I believe with edgy, there is no more /etc/inittab. This is probably
left over from your Dapper install. Edit your /etc/default/console-
setup file. There is a variable called
ACTIVE_CONSOLES="/dev/tty[1-6]" edit that to suite your needs,
reboot and that should fix it for you.
Thanks,
print
