ldm: ConsoleKit and Xsession location

https://bugzilla.redhat.com/show_bug.cgi?id=436912
(ldm) Launch all sessions via Xsession script
https://bugzilla.redhat.com/show_bug.cgi?id=435521
ConsoleKit support

I am thinking about a possible solution to these problems.  In both
cases ldm client needs to know about things on the server, however we
don't want it to ask during login because that would slow things down.
These things are:

* The location of the Xsession script on the server.  There are
currently 3 different locations hard-coded in ldm.
* Whether or not ck-launch-session is available and you want to use it.
  (Some distros might have Xsession itself use ck-launch-session.)

There are two ways we could approach this problem:
1) ldminfod can tell the client.
2) ldm could call a single standardized and hard-coded script name like
/usr/bin/ltsp-Xsession.  That script is provided in your ltsp-server
package as a wrapper around Xsession, allowing the distro to define
exactly how they want to run Xsession, where, and if they want
ck-launch-session or not.

I am preferring method #2 because this makes possible an ldm runtime
from any arbitrary distro to log into any other arbitrary LTSP server.
This might one day be crucial for preloaded Flash-based thin clients to
be compatible with any LTSP server.  It might also be a good idea
because of the possibility of future things like ck-launch-session that
could be added to ltsp-Xsession that ldm really does not need to know about.

ldm client knowing only a single hard-coded name keeps it simple, while
the complexity stays on the server where it belongs.

Untested /usr/bin/ltsp-Xsession:
#!/bin/sh
. /etc/ltsp/ltsp-Xsession.conf
exec $XSESSIONCMD $1

/etc/ltsp/ltsp-Xsession.conf:
XSESSIONCMD="ck-launch-session /etc/X11/xinit/Xsession"

My ltsp.spec would write an appropriate $XSESSIONCMD for the target
distribution into this file which is then installed when you install the
ltsp-server package.  Or the Fedora/RHEL version of
/etc/ltsp/ltsp-Xsession.conf might just source my
/etc/sysconfig/ltspdist file which is becoming my place to specify
distro-specific variables set by the package build (because I don't want
to rely on lsb_release).  The debian/  directory could do whatever it
wants within /etc/ltsp/ltsp-Xsession.conf that provides $XSESSIONCMD.

Thoughts?

Warren Togami
[email protected]




-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Register now and save $200. Hurry, offer ends at 11:59 p.m., 
Monday, April 7! Use priority code J8TLD2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net