[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[K12OSN] Re: K12OSN Digest, Vol 14, Issue 23


I am in the same boat now you are...read below.

Eric, I hacked my setup by dumping "getent passwd > /etc/passwd" and
disabling ldap account checking (it still auths/passwd via kerberos
thank goodness).  Thanks for the tip on nscd.  For some reason
everything I had read previously said to turn it off.

I've got extreemly slow logins (rest of the session runs fast). When a
client comes up, the screen stays gray for longer than usual, and then
when the user logs in, it pauses after they have entered their
password.  It almost seems like GDM is taking awhile to run the
pre/post/init scripts.  I once fixed a similar problem by running
gdm-safe-restart (I had a lab full of gray screens, and then one by one
they all blinked on.. it's not helping right now).  Try logging into
your server from another linux box via Xnest & XDMCP (I used tsclient to
configure the options). I get a black screen and then finally the login
screen (much longer than it used to be).  VNC is slow as well.

I do have systems that get wacked as well while the user is still using
them.  The only things I have done recently are:

setup vnc via the X module method

and ran a ton of updates yesterday AM that included Xorg.  BTW, I am
running 4.1.1

Henry Burroughs
Technology Director
Hilton Head Preparatory School
> ______________________________________________________________________
> From: Julius Szelagiewicz <julius turtle com>
> To: Support list for opensource software in schools. <k12osn redhat com>
> Subject: Re: [K12OSN] users kicked out on 4.2.1
> Date: Mon, 18 Apr 2005 09:33:42 -0400
> Hash: SHA1
> > --- Jim McQuillan <jam mcquil com> wrote:
> >
> >> But, the pinginterval is there for a reason.  To
> >> detect displays that
> >> have dissappeared or are hung up for some reason.
> >>
> >> That's how GDM knows that it should kill any child
> >> processes if a user
> >> turns off their terminal.
> >>
> >
> > Isn't this the feature that doesn't seem to work,
> > leaving servers with orphaned processes when a user's
> > terminal either locks up or is powered-off without
> > logging out properly?
> >
> > Maybe I should check my pinginterval setting and make
> > sure it's not set to zero...
> >
> > -Rob
> The continuing saga of users being kicked out on 4.2.1:
> I am doing the following things:
> 1. keep my fingers crossed, 2. knock on unpainted wood as all stations are
> still ok.
> I have done the following:
> 1. put the X ping interval at 0, 2 very carefully edited the lts.conf file
> removing all obsolete references.
> I am contemplating the following, if stations continue to fail:
> 1. return to the previous version of LTSP, specifically, use the /opt/ltsp
> and /tftpdir/ltsp from before upgrade. 2. switch to a different windows
> manager (IceWM) was ruled out - the users don't want to change.
> I'll keep you posted. julius
> Version: GnuPG v1.2.3 (GNU/Linux)
> iD8DBQFCY7c22LhlZOaj6vURAl+kAJ9DfE7KfMSSBET+nqfrkGbvO1MfNQCdG+MK
> n2sATNQi+HKLiBcPNMSR+sc=
> =vcUy

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]