>>>>> "DL" == Dwayne Lovelady <[EMAIL PROTECTED]> writes:
DL> In a snap, I was opening xterm and netscape windows on a machine
DL> running exceed. Then I decided to fire up xdm and set exceed for xdmcp
DL> query. Login window pops up, no problem. I go to login, window
DL> disappears and looks like it ready to go. Then the window reappears,
DL> asking me to login. Password and login were correct, but it just
DL> doesn't want to.
What follows is from my experience slaving NT machines running Exceed off
of some RH5.1 boxes.
The problem is probably that the default .xsession file runs a window
manager as the last thing it does. Because of Exceed, there's already a
window manager running, so you can't run something like Enlightenment.
(Perhaps you can if you reconfigure Exceed; I'm not sure.) Then the
.xsession fails, it exits, and XDM restarts.
Log in using the failsafe (f1 instead of enter after typing your password)
and make a .xsession file like
#!/bin/sh
xterm&
xterm&
xterm
make it executable, log out, and try again.
Note that the third xterm is magic in that exiting it exits the whole
session. You might want to change the title or something.
DL> I looked in the xdm-error.log file in /var/log and it just says there
DL> is an error running the script but I am clueless.
How about the .xsession-errors file in your home directory?
- J<
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
