vagrant Thanks for the reply.
>>> ltsp-server-standalone 5.5.1-1ubuntu2 >> >> and done the ltsp-build client. >> >> 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 > > Specifying SERVER should be redundant if your NBD/NFS server is the same > as your LTSP server. OK, I've taken that out. > > >> My pxe terminal boots OK, nothing unusual in syslog that I can see. >> >> With screen_01 shell, it does this weird thing where the console flops >> back and forth between a "Login:", and what appears to be a "#" root >> prompt. If you respond to the "Login:", it flops to "#", and says >> "command not found" if you type a command in response to "#", it says >> "Login incorrect". After an extended, variable time, it sometimes >> becomes possible to log in (I've created an account in chrooted >> /opt/ltsp5/i386). Then everything appears normal. It shows proper >> netstat -nr, everything seems to be mounted OK. > > You should probably stick to SCREEN_02 and higher. tty1 > (a.k.a. SCREEN_01) usually has a traditional login getty running on it, > and it's probably fighting with the shell screen script. Normally, tty2 > through tty6 also have login gettys running on them, but LTSP clears > those out at boot. Yes, that's it! If I change to SCREEN_02, "shell" works fine. Bizarre. It was not thus in previous versions of ltsp. > > >> 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. > >> 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. ldm: starts, but can't log in "no response from server, restarting". Syslog says: > Feb 13 10:36:21 ltsp12 ldm[1730]: calling rc.d pressh scripts > Feb 13 10:36:26 ltsp12 ldm[1730]: no response, restarting > Feb 13 10:39:11 server ldminfod[3875]: connect from 192.168.10.12 > (192.168.10.12) > Feb 13 10:36:28 ltsp12 ldm[1953]: started on client with IP address: > 192.168.10.12 > Feb 13 10:36:28 ltsp12 ldm[1953]: calling rc.d init scripts > Feb 13 10:39:12 server nbd_server[16218]: Spawned a child process > Feb 13 10:39:12 server nbd_server[3882]: virststyle ipliteral > Feb 13 10:39:12 server nbd_server[3882]: connect from 192.168.10.12, assigned > file is /opt/ltsp5/images/i386.img > Feb 13 10:39:12 server nbd_server[3882]: Can't open authorization file > /etc/ltsp/nbd-server.allow (No such file or directory). > Feb 13 10:39:12 server nbd_server[3882]: Starting to serve > Feb 13 10:39:12 server nbd_server[3882]: Size of exported file/device is > 363274240 > Feb 13 10:36:28 ltsp12 kernel: [ 61.425635] nbd9: unknown partition table > Feb 13 10:39:12 server nbd_server[3882]: Disconnect request received. > Feb 13 10:39:12 server nbd_server[16218]: Child exited with 0 > Feb 13 10:36:28 ltsp12 kernel: [ 61.430425] block nbd9: NBD_DISCONNECT > Feb 13 10:36:28 ltsp12 kernel: [ 61.430989] block nbd9: Receive control > failed (result -32) > Feb 13 10:36:28 ltsp12 kernel: [ 61.431073] block nbd9: queue cleared > Feb 13 10:36:28 ltsp12 ldm[1953]: authenticating with backend: ssh regards, Tim Johnston > > > live well, > vagrant > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
