very slow login times

[Luis Montes]

copy & paste got wierd on me there.
it should have been:

[default]
   SCREEN_07=ldm 
   LDM_DIRECTX=True
   SCREEN_08=shell

(each on its own line of course, in case this one doesn't work either)

Luis Montes wrote:
> My guess right now is that its neither  the network or the server.  
> After you type in a user/password on the login screen, switch over to 
> a different tty like ctl-alt-f8
>
> I have this in my lts.conf:
> [default]
>    SCREEN_07=ldm      LDM_DIRECTX=True
>    SCREEN_08=shell
>
> run top during the slow login time and let me know if you also have  a 
> pegged thin client.
>
> This slow login time has to be a bug. I've been using ltsp for years 
> and have never seen this before.
>
> Luis
>
>
> rmcdaniel at indata.us wrote:
>> This is interesting.  I am using a HP Proliant server with Dual Quad
>> Core cpu's, 4 GB memory, and about 210GB of storage.  I am also seeing
>> very slow bootup and login times.  I am suspecting that it has something
>> to do with my network.  When I run the resource monitor on the server,
>> nothing looks like it is getting close to maxing out.  I am running the
>> 32 bit version of the OS and my clients are HP T5530 with 128 MB of mem.
>>  Tomorrow I am going to look at my network and see if I have any
>> problems.
>>
>>
>> Ron McDaniel
>> rmcdaniel at indata.us
>>
>> -------- Original Message --------
>> Subject: Re: very slow login times
>> From: Luis Montes <monteslu at cox.net>
>> Date: Wed, November 05, 2008 2:12 pm
>> To: Development discussion of K12Linux <k12linux-devel-list at redhat.com>
>>
>> This has really become a problem. Waiting 3 to 4 minutes from login 
>> is too long.
>>
>> Any one have any ideas what script is eating up the thin client's cpu?
>>
>> I could really use some help with this.
>>
>> Thanks,
>>
>> Luis
>>
>>
>>
>>
>>
>> Luis Montes wrote:
>>  
>>> Boot up seems normal, but time from login to having gnome up is 
>>> about 4 and a half minutes.
>>>
>>> If I jump over to another tty on the terminal it looks like sh is 
>>> eating up most of the cpu and ram for that duration, though the 
>>> resources aren't completely tapped.
>>>
>>> The thin clients are disklessworkstations.com t150s. (32bit 500Mhz 
>>> via, 128MB ram). Top shows that during the login period I'm using 
>>> about 80MB of ram.
>>>
>>> The server is Fedora 9 64bit.
>>>
>>> Nothing particularly interesting either /var/log/messages on the 
>>> server or the client that I can tell, but I'm not sure what to look 
>>> for.
>>>
>>> Any idea which script this is that could be taking up all the cpu time?
>>>
>>> Thanks,
>>>
>>> Luis
>>>
>>> _______________________________________________
>>> K12Linux-devel-list mailing list
>>> K12Linux-devel-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/k12linux-devel-list
>>>
>>>     
>>
>> _______________________________________________
>> K12Linux-devel-list mailing list
>> K12Linux-devel-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12linux-devel-list
>>
>>
>>
>>
>> _______________________________________________
>> K12Linux-devel-list mailing list
>> K12Linux-devel-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/k12linux-devel-list
>>
>>   
>
>