gthomas@fraser.sfu.ca (Guy Thomas) writes:

quoted text
>Timo.Korvola@hut.fi (Timo Korvola) writes:

quoted text
>>In article <gthomas.734827612@sfu.ca> gthomas@fraser.sfu.ca (Guy Thomas)
>>writes:

quoted text
>>   I initialy installed the new kernel, 99p8,
>>   which caused xdm to fail.

quoted text
>>   - xdm comes up and presents login prompt
>>   - login takes username and passwd
>>   - seems to pass control to xinit
>>   - then snaps back to the login

quoted text
>>I've had the same problem, had to switch back to 0.99.7 to run xdm.

quoted text
>>It seems that xinit runs .xinitrc, but the user's clients aren't
>>allowed to connect to the server.  Putting xhost + in your Xstartup
>>disables the access control, so your clients (and anybody else's for that
>>matter) can connect, but I wouldn't recommend this on a network machine.

quoted text
>This behaviour may be related to NFS.  I have created anon privleged
>user with home directory on the local disk and was able to log in.
>All the other users on the system have directories mounted via NFS.

quoted text
>I will apply the patch that came out for the vm86 problem to see
>if it is the problem here.  

quoted text
>Watch this space.

Yup.  The susption was correct.  It was related to the access()
problem with the NFS code in 99p8.  Apply the patch that got released
for the vm86 problem and all was well again.

quoted text
>Guy


quoted text
>P.S.  clearing /tmp/.X0-lock and /tmp/.X0-unix/X0 cleared up
>the Server active error.  

quoted text
>Thanks to; Tor Arntsen, Jason A Kinner, James C. Tsiao, Ron Visser,
>Bill Woodward and any one else that I have have missed.