Re: [Ltsp-discuss] ltsp + ldap

2005-08-25 Thread Roberto Leiva M.
Roberto Leiva M. wrote: Breshears Doug P wrote: No, you pretty much ignore LTSP when setting up LDAP logins. You need to install an LDAP server (OpenLDAP) and the pam libraries to talk to the LDAP backend. You also need to set up nsswitch libs and in the end probably nscd(Name Server Caching

Re: [Ltsp-discuss] Local drives

2005-08-25 Thread Fajar Priyanto
On Monday 22 August 2005 18:37, Jim McQuillan wrote: Michael, We are indeed working on a much better solution to the whole issue of local drives, including USB and built-in floppy and cdrom drives. If you could take the time to update the LocalMedia wiki page with information about your

Re: [Ltsp-discuss] x terminal working very slow - is it normal?

2005-08-25 Thread Piotr Sobolewski
On Saturday 20 of August 2005 21:43, Piotr Sobolewski wrote: Hi, I just install an X terminal at my home. The server is Debian, 1 GHz, 256 MB RAM. The terminal is 60 MHz, 32 MB RAM. After installation I had problems with making X server (on terminal) work (you know, normal problems with

[Ltsp-discuss] MueKow for Redhat Enterprise

2005-08-25 Thread Ordway, Ryan
Has anyone tried putting together a MueKow environment for Redhat Enterprise Linux? I'm running LTSP 4.1.1 right now and I'm working on moving the execution of at least Firefox off of the server and onto our clients. We have about 30 terminals that we bought from disklessworkstations.com

[Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread Fajar Priyanto
Hi all, Another problem that I encounter is that dosemu takes 99% of cpu for each of it's instances. This becomes a performance problem in my LTSP configuration, where all the work is on the server. The dos program becomes very slow. Is it normal that dosemu takes 99% of cpu? Anyone has

Re: [Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread bob greatguy
Fajar, I have this problem in certain cases with the foxpro app that I run. It is only in rare and temporary cases, so I have not tried to fix it. However, there is a dosemu setting that you can change to control how much cpu it uses. Look for $_hogthreshold in dosemurc. bob On 8/25/05, Fajar

Re: [Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread Fajar Priyanto
On Friday 26 August 2005 05:29, bob greatguy wrote: Fajar, I have this problem in certain cases with the foxpro app that I run. It is only in rare and temporary cases, so I have not tried to fix it. However, there is a dosemu setting that you can change to control how much cpu it uses. Look

Re: [Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread Steve Dibb
Fajar Priyanto wrote: Hi all, Another problem that I encounter is that dosemu takes 99% of cpu for each of it's instances. This becomes a performance problem in my LTSP configuration, where all the work is on the server. The dos program becomes very slow. Is it normal that dosemu takes 99%

Re: [Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread Harry Sufehmi
*** REPLY SEPARATOR *** On 26/08/2005 at 05:21 Fajar Priyanto wrote: Hi all, Another problem that I encounter is that dosemu takes 99% of cpu for each of it's instances. This becomes a performance problem in my LTSP configuration, where all the work is on the server. The dos

Re: [Ltsp-discuss] Dosemu takes 99% cpu

2005-08-25 Thread kemas
hi, $_hogtreshold doesn't seem do much different, because default setting already set to 0 (nicest). i suppose dosemu should be run as local apps, but anyone had tried this? thanks kemas - Original Message - From: Harry Sufehmi [EMAIL PROTECTED] To: ltsp-discuss@lists.sourceforge.net

Re: [Ltsp-discuss] MueKow for Redhat Enterprise

2005-08-25 Thread jam
On Friday 26 August 2005 11:08, [EMAIL PROTECTED] wrote: Has anyone tried putting together a MueKow environment for Redhat Enterprise Linux? I'm running LTSP 4.1.1 right now and I'm working on moving the execution of at least Firefox off of the server and onto our clients. We have