Problem getting login on tty1-tty6.

Stef Bon stef at bononline.nl
Tue Nov 24 09:32:20 GMT 2009


Michael Biebl wrote:
> I rather suspect that Stef is missing to generate the runlevel event,
> so the ttys are not started automatically.
> I.e. if you have a job depending on runlevel X you have to call
> telinit X at some point during the boot process.
>
> In Debian/Ubuntu this is done in rc-sysinit.conf, which parses
> /etc/inittab if existent and the runs
> telinit "${DEFAULT_RUNLEVEL}"
>
> Michael
>
>
>
>   
Well, this is ok on my system. My rc-sysinit.conf does the same. It 
reads the DEFAULT_RUNLEVEL
from inittab and/or parameters from the kernel, and at the end trigger 
the runlevel event.

After that, the scripts that belong to this runlevel (according to 
sysvinit) are started by rc.conf, which is triggered by the
runlevel event:

start on runlevel [0123456]

I cannot do this for the ttyX.conf files, because they have to be 
started *after* the starting of these runlevel scripts is ended. I've 
tried this,
but then alogin appears on the console ate the same time output from 
these script gets on the screen, so the ttyX.conf files have to be 
started later.

The starting of these scripts goes ok, but when the starting of these 
scripts is finished, a login should appear. Now that does not happen.
I can login with ssh, because it's started properly.

I'm thinking, the event runlevel is not ended, but the system is still 
"in" runlevel as before. So, this runlevel does not stop or change it's 
value,
or it's stopped. (again my question: the runlevel is a state the system 
is in, not a job right?)
The starting of the ttyX.conf files wait for the runlevel to stop, which 
will not happen. They should wait for the rc.conf to stop.

Is this right thinking?

Stef



More information about the upstart-devel mailing list