Hi
In the Gutsy or so days I took the whole chroot for ltsp, wrapped it with the
tools in a rpm and have been using it ever since on CentOS for customers and
SuSE for me.
It has a single irritating 'feature' logout with autologin set is immediate
relogin.
Curiosity, features and fixes led me to experiment: I installed intrepid, then
the ltsp stuff as per the wiki.
For the first time ever, my clients do not start X. All is normal until ldm
then this is logged continuously:
Feb 1 11:54:40 neptune ldminfod[6176]: connect from 192.168.5.121
(192.168.5.121)
Feb 1 11:54:41 neptune ldminfod[6179]: connect from 192.168.5.121
(192.168.5.121)
Feb 1 11:54:41 neptune ldminfod[6182]: connect from 192.168.5.121
(192.168.5.121)
I modified ldm to log to syslog back when. I used that version of ldm here and
got:
Feb 1 11:36:17 ws121.home ldm: [xauth_command] cmdline:/usr/bin/xauth -i -n -
f /root/.Xauthority generate :7
Feb 1 11:36:18 ws121.home ldm: [ldm_spawn] cmdline:/usr/bin/xauth -i -n -f
/root/.Xauthority generate :7
Feb 1 11:36:18 ws121.home ldm: [xauth_command] cmdline:/usr/bin/xauth -i -n -
f /root/.Xauthority generate :7
Feb 1 11:36:19 ws121.home ldm: [ldm_spawn] cmdline:/usr/bin/xauth -i -n -f
/root/.Xauthority generate :7
In neither case was X spawned.
The only funny I'm doing is ONE not TWO ethernet interfaces.
Before I jump in trying to find what is wrong, can anybody say "Oh yeah that
is because ... "
Of course the usual suspects are done: ltsp-sshkeys, ltsp-image
Thanks
James