Slawek Drabot kirjoitti:
> is there a way to get a log of errors that caused the boot process to crash?
Be sure that there is no other dhcpd server on your ltsp5 network. In
one case Buffalo wlan box prevented thin clients to boot to the login
screen. After shutting down Buffalo's own dhcpd server thin clients
booted all the way to the login screen.
/var/log/daemon.log (1-3) and /var/log/auth.log (4) should tell you
something. Here is a boot process for a thin client:
1.
Dec 18 20:49:21 ubuntu dhcpd: DHCPDISCOVER from 00:22:15:15:4b:4c via eth0
Dec 18 20:49:21 ubuntu dhcpd: DHCPOFFER on 192.168.1.200 to
00:22:15:15:4b:4c via eth0
2.
Dec 18 20:49:53 ubuntu in.tftpd[6526]: tftp: client does not accept options
3.
Dec 18 20:50:34 ubuntu nbdrootd[6546]: connect from 192.168.1.200
(192.168.1.200)
Dec 18 20:50:34 ubuntu nbd_server[6547]: connect from 192.168.1.200,
assigned file is /opt/ltsp/images/i386.img
Dec 18 20:50:34 ubuntu nbd_server[6547]: Size of exported file/device is
383410176
Dec 18 20:50:42 ubuntu ldminfod[6548]: connect from 192.168.1.200
(192.168.1.200)
4.
Dec 18 20:50:43 ubuntu sshd[6551]: Accepted password for ltsp001 from
192.168.1.200 port 51215 ssh2
Dec 18 20:50:43 ubuntu sshd[6551]: pam_unix(sshd:session): session
opened for user ltsp001 by (uid=0)
Best Regards Asmo Koskinen.
------------------------------------------------------------------------------
_____________________________________________________________________
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
