On Tue, 2005-11-01 at 12:20 -0500, Peter Billson wrote: > I have a weird problem with KDM's auto login on one terminal. > > About once a day this one particular terminal refuses to auto login. > The 30+ other terminals work fine. > > Every other terminal at every other location I have works fine. > > I can manually log in as the user, no problem. > > If I let the terminal sit overnight, it will log in OK the next morning. > > I have erased the user's home directory and started from scratch but > no joy.
I seem to be having similar problems periodically. We have about 30
thin clients spread throughout the library and every so often one or
more of them will freeze up after loading the desktop background but
never makes it completely to its normal operating mode, running Firefox
and IceWM. I see some strange syslog errors like:
Alert summary: 2 records
---------------------------------------
moscow Nov 21 10:01:26 kdm: ws503:0[2389]: Cannot connect to
ws503:0, giving up
Nov 21 10:01:26 kdm: Display ws503:0 cannot be opened
Or:
Alert summary: 1 records
---------------------------------------
moscow Nov 18 13:40:03 kdm: ws103:0[11895]:
pam_setcred(DELETE_CRED) for ws103 failed:
System error
I've not had a lot of time to track down the problem. Power cycling the
client will fix the problem.
This is on a Redhat Enterprise 4 based LTSP server. They are all on a
private 100mb VLAN. The LTSP server is also connected to the rest of the
network. LTSP user accounts are stored in /etc/{passwd,shadow} but
non-LTSP accounts are in an LDAP directory, so the system is configured
to look first in files and then in LDAP for user info.
Has anyone else noticed problems like this?
Ryan
--
Ryan Ordway E-mail: [EMAIL PROTECTED]
Unix Systems Administrator [EMAIL PROTECTED]
Oregon State University Libraries
121 The Valley Library Office: The Valley Library #4657
Corvallis, OR 97331
signature.asc
Description: This is a digitally signed message part
