Thanks, Gadi. First, some new info, then the answers to your questions. Two pieces of test hardware: 1: HP t5720, 2: HP nx9420 laptop. When booting both of these from 10.10, neither honours the SHUTDOWN_TIME variable. Running tcpdump -n -i eth0 port 123 on the LTSP/ntp server, I see the t5710 querying on bootup. I do not see the nx9420 querying.
On Fri, Mar 25, 2011 at 11:09 AM, Gideon Romm <[email protected]> wrote: > Have you opened up a local xterm (ltsp-localapps xterm after logging > in through ldm) and executed "ntpdate <server>" in the local xterm? Logged into the nx9420 via ssh this appears to work: root@tc-laptop-HP:~# ntpdate 172.21.35.0 25 Mar 11:15:43 ntpdate[2206]: step time server 172.21.35.0 offset 3678.981037 sec root@tc-laptop-HP:~# date Fri Mar 25 11:15:46 MDT 2011 > Also, I am hoping you are setting the TIMEZONE variable, as well. > TIMESERVER will simply set the time but in most cases it will still be > UTC time and not your local time unless you set TIMEZONE. No, but the timezone (MDT) is correct, and the time is correct (after manually running ntpdate). Still, the SHUTDOWN_TIME variable doesn't work even when the system time reaches the appointed shutdown time, on either piece of hardware. db ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _____________________________________________________________________ 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
