-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Brian K. White wrote:
| ----- Original Message -----
| From: "jdd sur free"
| Cc: "suse"
| Sent: Saturday, August 02, 2008 10:29 AM
| Subject: Re: [opensuse] Console login before x login
|
|
| Tamas Sarga a écrit :
|
|> With OpenSUSE after reaching runlevel 5. If I change to a console
|> (Ctrl-Alt-Fx), before login by KDM,
|
| there is a problem, I don't have this feature. did you try the left
| bottom menus in the login screen (menu "system"=, a console login is
| vailable
|
| or if x startup fails and fallbacks
|> to console, then {&HOSTNAME} login: doesn't appear.
|
| this is odd, usually fallback is a console (I happen to have used this
| several time yesterday triyng to setup a dual screen). I suppose
| changing of console or control C didn't work?
|
|> In 10.3 I can boot up the computer to the default runlevel 5, and use
|> the virtual consoles without a graphical login, if the task what I have
|> to do doesn't require GUI.
|
| do you have the same result with default (non nvidia) driver?
|
| ---------
|
| He's not ignorant of Ctrl-Alt-F1
| What he's saying basically is that the xdm rc script is running before
the console gettys get run, and that it's blocking the rest of the
startup process until it finisheds, but it never finishes, and so init
never reaches the point where it would start the console gettys. And if
that's so, then it shouldn't matter what video driver is in effect. the
more critical parts of the server should never depend upon the video
hardware.
|
| It appears that what he's describing is entirely possible.
|
| In /etc/inittab, the line that starts all the runlevel 5 rc scripts:
| l5:5:wait:/etc/init.d/rc 5
| ... has the wait action flag, and comes before the lines that start
the console gettys:
| 1:2345:respawn:/sbin/mingetty --noclear tty1
| 2:2345:respawn:/sbin/mingetty tty2
| 3:2345:respawn:/sbin/mingetty tty3
| 4:2345:respawn:/sbin/mingetty tty4
| 5:2345:respawn:/sbin/mingetty tty5
| 6:2345:respawn:/sbin/mingetty tty6
|
| So, init waits for all the /etc/init.d/rc5.d/S* scripts to finish
before proceeding on to start the console gettys.
|
| rc5.d/S04earlyxdm does some stuff that doesn't look at first glance
like it should be at too much risk of ever blocking like that itself,
then it ends by running init.d/xdm, which of course is what's hanging...
|
| init.d/xdm has... doh, I don't have init.d/xdm.
|
| In any event, there are several possible ways to improve the behavior.
|
| Ultimately the "this could ever hang or crash" parts of xdm should
probably be launched in the background so that the script can proceed
and finish, and so the rest of the runlevel 5 rc scripts can proceed and
finish, regardless of if the x server happens to work or not.
|
| One thing you may be able to do quick-n-dirty for now is just set
RUN_PARALLEL in sysconfig.
| (vi /etc/sysconfig/boot, or, yast, System, /etc/sysconfig editor,
System, Boot, RUN_PARALLEL, yes)
| That should make all rc scripts run in the background, which is an
ugly but easy way to get init.d/xdm to run in the background.
|
| Then the parent script (/etc/init.d/rc) should return right away
regardless if any of the rc scripts crash or hang, and so /etc/inittab
should proceed right on to the console getty lines right away.
|
| On my 11.0 boxes it turns out run_parallel is already on by default so
presumably yours is already on too, so possibly this won't help you. But
check it at least, maybe you turned that option off and maybe that's the
problem?
|
| Another possible approach is move the getty lines in /etc/inittab so
they come before the init.d/rc lines.
| Doesn't look like that would cause any problems, but you never know.
|
| Another possible approach is remove the wait flag from the rc5 line,
change it from :wait: to :once:
| I don't know if that's a great idea or not either. Seems like it
should be fairly harmless, the rest of inittab, including
/sbin/mingetty, looks like it should be able to run without needing any
rc scripts to get networking up or mount filesystems etc... but, 10.3
had the same wait action on the rc lines in it's inittab too so there
must be a reason...
|
Hi,
Thanks for your reply. The situation is not exactly this, but something
similar. In more deep see my other post to this thread!
So the problem that xinet.d's failure blocks to reach runlevel 5
somehow. But KDM login kick it through somehow.
I'm confused, how could this happen.
I'm pretty sure that a daemon's failure shouldn't block the boot process.
Cheers,
Tamas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFIlYqnsuVyj8v2Zy4RAsDDAKCEVzsHKQTIiBCOxkZ86vQ48DyYrwCfUt3T
5GCOYO+0m7RZ0B09/i12LNg=
=go0M
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse+help@opensuse.org