From: Volker T. <vol...@di...> - 2003-09-16 09:23:28
|
Greetings! On Tue, 16 Sep 2003 11:41:14 +0800 Craig Ringer <cr...@po...> wrote: > > Normally an 'indirect' request brings up a gui chooser maintained by > the display manager contacted, allowing the user to pick a server > based on name, load, etc... but I wouldn't be surprised if you could > cut that step out and immediately contact a login server picked by the > initial XDMCP server contacted. Thanks, good idea. I want to have an automatic selection as the intended users are comparatively... hm... let's say just office computer users. I'll dig into that. At first glance I could adapt a chooser according to the needs. I'll report back. > As for the work involved - it may involve modifying [xgk]dm, or may be > as simple as telling the display manager to run an alternative client > for indirect requests, one that knows what to do. See above - usually you can tell them simply tell to use a different chooser. Which I will provide then. > I'm pretty sure you can get the server load average over XDMCP, so > that might be one possible measure to use when deciding what hosts to > send clients to. Seems so. > In summary, what I'm suggesting is the use of a single server (with > failover) to handle the initial indirect XDMCP requests from clients. > Those clients will be sent the real host to connect to, and will make > another XDMCP request to the given host - not talking to the initial > server again until X is restarted on the client, usually at logout. > The initial server can then keep track of which servers are currently > accessable, and which have lower load, then direct clients > appropriately. Good idea. I'll play with that. Thanks Volker Tanger -- ITK-Security DeTeWe AG & Co. KG Fon +49 30 6104-3307 Fax +49 30 6104-3435 http://www.detewe.de/ |