On 2015-02-12, Tim Johnston wrote:
>>>> ltsp-server-standalone              5.5.1-1ubuntu2
...
>>> I have /var/lib/tftpboot/ltsp5/i386/lts.conf as:
>>>
>>>   >[default]
>>>>    SERVER=192.168.10.1
>>>>     SCREEN_01=shell
>>>>     SCREEN_02=telnet
>>>>     SCREEN_03=kiosk
>> ...
>>>>     TELNET_HOST=192.168.10.1
...
>>> screen_02 says "press any key to connect". But it doesn't connect, it
>>> drops to a "telnet>" prompt. But can then "open 192.168.10.1" to connect
>>> to the server works fine.
>>
>> That sounds odd.
>
> Yes. This particular terminal is intended as a telnet text terminal, so 
> it would be good if I could get this to work properly.

There was a fix committed upstream in the telnet screen script that
isn't present until ltsp 5.5.4:

  
https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2599/client/share/ltsp/screen.d/telnet

Ubuntu trusty only has 5.5.1...

It's a simple patch:

--- a/client/share/ltsp/screen.d/telnet
+++ b/client/share/ltsp/screen.d/telnet
@@ -22,7 +22,7 @@
 # the default of '192.168.67.1'
 #
 
-if [ $# -ge 1 ]; then
+if [ -n "$1" ]; then
     TELNET_ARGS=$*
 else
     TELNET_HOST=${TELNET_HOST:-${SERVER}}


That may fix your issue with telnet.


>>> ldm and startx don't work at all, nothing logged.
>>
>> By not work at all, you mean nothing shows on the screen at all? Or a
>> login screen shows but doesn't successfully login?
>>
>> They're not configured to run in your above setup. You'd typically add
>> them as SCREEN_07=ldm or SCREEN_07=startx in lts.conf. If you can get
>> the shell working on one of the other ttys, that would be your best
>> avenue for debugging...
>
> startx: blank screen, nothing logged that I can see.
>
> BUT, from shell "X -query 192.168.10.1" works fine.

I think this essentially the same issue to the telnet one, fixed in:

  https://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2598


> ldm: starts, but can't log in "no response from server, restarting".

That's typically the result of outdated ssh keys, which should be fixed
on Ubuntu (or other systems using NBD) by:

  ltsp-update-sshkeys
  ltsp-update-image

Either that, or it's trying to connect to some other server...


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to