Preliminary remark: We don't have ltsp installed, but another solution from a
german company called Gonicus, which works fine already for 5 years. This
setup is quite similiar to ltsp5, based on native Debian package management.
To update our installation we intend to switch to ltsp5.
But this
On Tue, Jul 31, 2007 at 09:01:03AM -0500, Jim Kronebusch wrote:
Or maybe the xdmping ots-4 -v -t 1 command already does this, in
that case disregard my comments :-)
xdmping is not homebrewn by us. It's available e.g. at:
http://frmb.org/xdmchoose.html
Also, would the xdmping command work
The amount of logged in users is not the only parameter to decide the load of
a server. We have a range of terminal servers with different architectures and
power. At least the number of processors, speed, and ram must be taken into
account.
We are using xdmping for load balancing, which
The Future is Already Here - It's Just Not Evenly Distributed
Francis, you're funny. Let's get the future distributed then :-)
--
This message has been scanned for viruses and
dangerous content by the Cotter Technology
Department, and is believed to be clean.
Hi,
For simple loadbalancing, maybe I would let the LDM_SERVER as is and
create a new variable for matter, for example : LDM_SERVERS_LIST. I
understand that for simple loadbalancing, servers state won't be used
and only a randomize on the list will be done. That's good and scalable.
But at
We're still needing a good method for getting network auth going. I don't
want to say too much, but Matt Oquist and I banged around a couple of
ideas in #edubuntu a few days ago, and he's begun work on pam/nss module
that will do what we want without the need for pushing ldap down to the
On Sun, 29 Jul 2007 17:50:41 -0400, Francis Giraldeau wrote
Jim Kronebusch a écrit :
LDM_SERVER could be a space separated list of hosts. Something
like
LDM_SERVER=192.168.0.254 192.168.0.253 192.168.0.252
Or, names, if the administrator sets things up in the
chroot for /etc/hosts
On 7/30/07, Jim Kronebusch [EMAIL PROTECTED] wrote:
I don't know much about how this would or does work, but if there was an
constant ssh
connection between servers could this also be a way to collect data to help
apps such as
Student Control Panel or TeacherTool better manage users across
On Mon, Jul 30, 2007 at 12:11:37PM -0500, Jim Kronebusch wrote:
Then make the default server the one with the least amount of logged in users?
The amount of logged in users is not the only parameter to decide the load of
a server. We have a range of terminal servers with different architectures
Jim Kronebusch a écrit :
LDM_SERVER could be a space separated list of hosts. Something
like
LDM_SERVER=192.168.0.254 192.168.0.253 192.168.0.252
Or, names, if the administrator sets things up in the
chroot for /etc/hosts and/or resolve.conf.
Glad to see you're working on this, I
On Fri, Jul 27, 2007 at 11:27:38AM -0400, Francis Giraldeau wrote:
For simple loadbalancing, maybe I would let the LDM_SERVER as is and
create a new variable for matter, for example : LDM_SERVERS_LIST. I
understand that for simple loadbalancing, servers state won't be used
and only a
On Fri, Jul 27, 2007 at 03:15:27PM -0500, Jim Kronebusch wrote:
I would really like to see LDM_SERVER be able to accept fully qualified dns
names. Then
I could simply point LDM_SERVER=ltsp.mydomain.com and set up a round robin A
record in
DNS where ltsp.mydomain.com resolves to either a
Scott Balneaves wrote:
On Fri, Jul 27, 2007 at 11:27:38AM -0400, Francis Giraldeau wrote:
For simple loadbalancing, maybe I would let the LDM_SERVER as is and
create a new variable for matter, for example : LDM_SERVERS_LIST. I
understand that for simple loadbalancing, servers state won't
Scott Balneaves wrote:
On Fri, Jul 27, 2007 at 03:15:27PM -0500, Jim Kronebusch wrote:
I would really like to see LDM_SERVER be able to accept fully qualified dns
names. Then
I could simply point LDM_SERVER=ltsp.mydomain.com and set up a round robin A
record in
DNS where
Just giving people a status update on where ldm2 is at.
So, over the last couple of days, here's what's working:
Scripted greeter now working.
Indication of password failure, and password re-entry now working.
Password expiry working.
Autologin working.
Support for LDM_DIRECTX working.
New rc.d
Hi Scott,
Scott Balneaves a écrit :
Just giving people a status update on where ldm2 is at.
So, over the last couple of days, here's what's working:
Scripted greeter now working.
Indication of password failure, and password re-entry now working.
Password expiry working.
Autologin working.
LDM_SERVER could be a space separated list of hosts. Something
like
LDM_SERVER=192.168.0.254 192.168.0.253 192.168.0.252
Or, names, if the administrator sets things up in the
chroot for /etc/hosts and/or resolve.conf.
Glad to see you're working on this, I think all your suggestions
17 matches
Mail list logo
