Customizing Edubuntu's LTSP client to start another session

[S. J. van Harmelen]

On Tue, 2007-10-16 at 14:05 +0100, Gavin McCullagh wrote:
> Hi,
> 
> On Tue, 16 Oct 2007, S. J. van Harmelen wrote:
> 
> > So I did another test. I did a default ldm session and then tried to
> > manualy start /usr/lib/ltsp/screen.d/rdesktop. But this resulted in the
> > same behavior, and so I still could not check anything.
> > 
> > I find this rader strange though. The rdesktop script I'm trying to use
> > is file offert by Edubuntu it self. It's in the defult install off Gutsy
> > so I guess I should expect it to work out-of-the-box? Right?
> 
> Probably, though gutsy is still not released (albeit very close).
> 
> Did you try this:
> 
> > > You could check the rdesktop server and see are any connections being
> > > refused or if any connection is coming in from the client (tcpdump would be
> > > a good bet for this).
> 
> It may as you say be a bug, but this sort of information would tell us if
> the thin client is managing to get a connection out onto the network.  If
> it is a bug, now's the time to fix it.

Ok, did a tcpdump on a server in between the client and the RDP server
but did not receive any data from to client to the server at all!

> 
> You could install openssh-server into the kiosk.
> 
> 	sudo chroot /opt/ltsp/i386 apt-get install openssh-server
> 	sudo ltsp-update-image
> 
> and reboot the thin client.  Then you should be able to ssh into the thin
> client and try the previous tests.  You will get an error from the
> openssh-server install, but it should work anyway.  You can then remove it
> afterward.

Great advice!! Thanks!! I did this right away. After restarting the
client I can now login to see what's going on. And that is:

    1 ?        Ss     0:01 /sbin/init
 1943 ?        S      0:00 nbd-client 192.168.0.2 2000 /dev/nbd0
 2092 ?        S<s    0:00 /sbin/udevd --daemon
 2659 tty1     Ss+    0:00 /sbin/getty 38400 tty1
 2899 ?        Ss     0:00 /sbin/syslogd -u syslog
 3029 ?        Ss     0:00 /sbin/klogd -P /var/run/klogd/kmsg
 3032 ?        S      0:00 /bin/dd bs 1 if /proc/kmsg
of /var/run/klogd/kmsg
 3351 ?        Ss     0:00 /usr/sbin/sshd
 3519 ?        Ss     0:00  \_ sshd: root at pts/0 
 3531 pts/0    Ss     0:00      \_ -bash
 3809 pts/0    R+     0:00          \_ ps afx
 3436 ?        S      0:00 /bin/sh /usr/lib/ltsp/screen.d/rdesktop
 3799 ?        S      0:00  \_ /usr/bin/xinit /usr/bin/rdesktop -u  -a
15 -f 212.45.52.101 -- :6.0 tty7
 3800 tty2     S<s+   0:00      \_ X :6.0 tty7
 3456 ?        S<     0:05 /usr/bin/pulseaudio --system --disable-shm
--no-cpu-limit --resample-method=trivial --high-priority -L
module-detect -L module-
 3465 ?        Ss     0:00 /usr/bin/ltspfsd
 3473 ?        R      0:00 /usr/bin/python /usr/sbin/cdpinger cdrom
root at ltsp:~# ping 212.45.52.101
PING 212.45.52.101 (212.45.52.101) 56(84) bytes of data.
64 bytes from 212.45.52.101: icmp_seq=1 ttl=54 time=16.9 ms
64 bytes from 212.45.52.101: icmp_seq=2 ttl=54 time=15.4 ms

So you can see it can ping the requested address. Anything odd about
this process list? Does process  3799 look okay? As this is the one that
sould start rdesktop.

It seems this process is the one that keeps respawning as the PID keeps
changing...

Any tips? 

Sander



Any 
> 
> Gavin
> 
>