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

Re: [K12OSN] users kicked out on 4.2.1



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Hi !
> I was just reading this mail and noticed this
> "Maybe I should check my pinginterval setting and make
>> > sure it's not set to zero..." observ not set to zero.
> you just said that you did set it to zero.
> Dont know if it helps but thought i should mention it !
>
> cheers Kjell Andersson
>
> ----- Original Message -----
> 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 (EDT)
>
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> 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
>>
>
Kjell, nice try, but the timeout value is set to 0. This helped a lot, but
there were still hangups. I added gdm-reset to the nightly cron job and
the incidence went down to almost nothing - 2 hangups in 3 days. I still
don't know the cause.
julius

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFCe2GI2LhlZOaj6vURAh0VAKCKHLc64Jk21hpZ+tKH2c/SnZhILQCfcyuK
0nxvpQQ++XgQf27oTyEhzQc=
=NEfv
-----END PGP SIGNATURE-----


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