Richard-
On the server use the KDM configuration utility to make sure that
KDM (which is the display manger your using) is configured to handle
XDMCP. Also on a running client boot to runlevel 3 (SCREEN_01 = shell)
and confirm that var is being linked to /tmp/var and that the
permissions are
Op woensdag 2 maart 2005 22:18, schreef Evan Hisey:
On the server use the KDM configuration utility to make sure that
KDM (which is the display manger your using) is configured to handle
XDMCP.
That is what I checked with netstat and checking the config files... I can
connect to the server
Ricahrd
Also on a running client boot to runlevel 3 (SCREEN_01 = shell)
and confirm that var is being linked to /tmp/var and that the
permissions are right on tmp.
The client does not start up, it hangs there :(
I found another error msg, reported earlier in the boot that I'm
Op woensdag 2 maart 2005 22:18, schreef Evan Hisey:
Also on a running client boot to runlevel 3 (SCREEN_01 = shell)
and confirm that var is being linked to /tmp/var and that the
permissions are right on tmp.
A quick followup on this one:
There is no /var!
The /tmp permission are 755 owned by
Richard-
Right, I ithink it gets created the first time a client boots when
it links to /tmp/var. You will have to get a clinet to boot befor you
can see what tmp/ permissions really are becuase it is a mounted
ramdisk on the clients.
Evan
On Wed, 2 Mar 2005 23:20:21 +0100, Richard Bos [EMAIL
Richard,
Did you install LTSP-4.1 over the top of LTSP-3 ?
If so, try moving the directory out of the way, and re-installing
ltsp-4.1.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 2 Mar 2005, Richard Bos wrote:
Op woensdag 2 maart 2005 22:18, schreef Evan Hisey:
Also on a running client boot
Op dinsdag 1 maart 2005 23:32, schreef Richard Bos:
I can provide the following information
I forgot some information:
From dhcp.conf
host ws200 {
hardware ethernet 00:E0:18:90:90:38;
fixed-address 192.168.4.200;
filename /lts/vmlinuz-2.4.26-ltsp-2;
}
