On Fri, 2002-09-27 at 06:19, Kim Led Bendtsen wrote:
> After booting up, the client freezes a couple of seconds after the login
> manager shows. How can I get further and find out what courses the crash?
> 
> I suspect the trouble lies with the server. When the server computer boots
> (redhat 7.3) it first shows the ltsp login promp and afterwards switches
> to the 'normal' redhat login manager. I think the crash accurs when the
> standard (redhat 7.3) login manager begins at the client, but how do I
> find out whether this is the problem
> 
> Best regards
> 
> Kim

You can edit /opt/ltsp/i386/etc/lts.conf and set RUNLEVEL = 3 (I would
do it for a specific terminal).  Restart the terminal, then run
/tmp/start_ws.  Do you see any errors?

Do you see any errors in your system log (/var/spool/messages on Red
Hat)?

Don't worry about the login prompt "switching", it isn't a problem. 
What you are seeing is this:
1) Start X server
2) X Server queries the LTSP server
3) GDM on LTSP server runs /etc/X11/gdm/Init/Default, which puts the
LTSP logo on the screen
4) GDM on LTSP server runs /etc/X11/gdm/gdm.conf, which puts the Red Hat
logo on the screen.

Between versions 7.2 and 7.3, Red Hat changed how they put their logo on
the screen.  The LTSP setup scripts don't allow for that; however, it
isn't that big a deal, and no one's gotten around to changing it.  The
relevant line is
BackgroundProgram=/usr/bin/xsri --redhat-login --run

If you don't like it, you can change this line to:
BackgroundProgram=/usr/bin/xsri \
  -geometry +5+5 -avoid 300x250 \
  -keep_aspect \
  /etc/X11/xdm/ltsp.gif \
  --run

-David


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to