On Wed, Mar 23, 2011 at 4:24 PM, Michael Pope <[email protected]> wrote:
> */var/lib/tftpboot/ltsp/i386/lts.conf* > TIMESERVER = 10.1.1.10 > RCFILE_01 = /etc/ltsp/ntpdate > > > $ sudo mkdir /opt/ltsp/i386/etc/ltsp > $ sudo vim /opt/ltsp/i386/etc/ltsp/ntpdate* > > /opt/ltsp/i386/etc/ltsp/ntpdate** > * > #!/bin/bash > if [ -n $TIMESERVER ]; then > ntpdate $TIMESERVER & > else > ntpdate pool.ntp.org > fi > > $ sudo chmod +x /opt/ltsp/i386/etc/ltsp/ntpdate That's interesting, but if I run ntpdate manually on a client I get "the NTP socket is in use, exiting". Then this: ~# ps aux | grep ntp ntp 1934 0.0 0.0 4352 1208 ? Ss 15:24 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:112 But if I sniff packets on the ltsp server (which is also my TIMESERVER), filtering for port 123, I see nothing. If I do "parallel-ssh -i -h tc-list "date && hwclock"" (which queries all my clients for system and BIOS time), it appears they are not synchronized. And on the topic of the SHUTDOWN_TIME variable, it does not appear to work for me, even after doing "hwclock --tzsync" to bring the system and BIOS time into the same timezone and trying again. I'm not sure what's missing here. I do have cron installed in the chroot. 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
