Have you opened up a local xterm (ltsp-localapps xterm after logging
in through ldm) and executed "ntpdate <server>" in the local xterm?

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.

-Gadi

On Fri, Mar 25, 2011 at 12:56 PM, David Burgess <[email protected]> wrote:
> On Fri, Mar 25, 2011 at 9:37 AM, David Burgess <[email protected]> wrote:
>
>> I built a fresh client image on a 10.04 server and both the
>> SHUTDOWN_TIME and TIMESERVER options are working. I assumed I had
>> messed something up when building my 10.10 image and broken these, so
>> I then rebuilt my 10.10 client image from scratch, but was surprised
>> to see that neither of these options is working on the fresh 10.10
>> image.
>
> I stripped my 10.04 chroot to exactly mirror the 10.10 chroot:
>
> # deborphan -an
> main/misc                 ltsp-client
> main/misc                 lockfile-progs
> main/net                    tcpdump
> main/admin                acpid
> main/metapackages   linux-image-generic
> main/net                   openssh-server
> main/net                    ltspfs
> main/admin                dmsetup
> main/metapackages   ubuntu-minimal
> main/admin                deborphan
>
> Still, the 10.04 client queries the TIMERSERVER and shuts down on
> schedule, while the 10.10 client does neither.
>
> The only other difference I can think of is that the 10.10 client is
> on a vlan with no DNS and no routing, while the 10.04 client has DNS
> and internet access. Both are able to connect to their respective LTSP
> server. Both connect to the same Windows RDP server (which listens on
> both vlans with separate NICs), and both should be using the same
> TIMESERVER (using separate IP addresses, corresponding to the
> connected vlan).
>
> I've looked at the cron files and ntpdate files in the chroot, but I
> don't know enough about the system to spot any differences or
> problems. I haven't modified any of these since building the chroots
> or client images.
>
> I think I can say with a high degree of confidence that there appears
> to be a regression from Ubuntu 10.04 to 10.10 with regards to the
> TIMESERVER and SHUTDOWN_TIME variables, in that they don't work for
> reasons that I have not been able to discern thus far.
>
> 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
>

------------------------------------------------------------------------------
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

Reply via email to