TIMESERVER with systemd might be broken (debian stretch)

On 2017-05-08, wforumw wrote:
> I use LTSP 5.5.9 (Debian Stretch). I would like to configure NTP for all
> FAT Clients. If I use NBD image it does not take the option TIMESERVER
> in lts.conf.

It looks like you reported this issue to the ltsp-discuss list:

  https://sourceforge.net/p/ltsp/mailman/message/35810155/

As I understood it, you responded that using the lts.conf from the
correct tftp directory fixed the issue.

Is this new bug a different issue somehow?

live well,
  vagrant

That's true but I was to fast.

The lts.conf is located in the correct tftp directory but still didn't
updated the correct time.

You can find the ltsp-info here

https://pastebin.com/kUqLZRF3

And ltsp_config_env here

https://pastebin.com/DpsEaXtB

The NTP server is working as all our servers connect to it.

And I can reach the NTP Server from the client

On 05/08/2017 06:13 PM, Vagrant Cascadian wrote:
> On 2017-05-08, wforumw wrote:
>> I use LTSP 5.5.9 (Debian Stretch). I would like to configure NTP for all
>> FAT Clients. If I use NBD image it does not take the option TIMESERVER
>> in lts.conf.
> It looks like you reported this issue to the ltsp-discuss list:
>
> https://sourceforge.net/p/ltsp/mailman/message/35810155/
>
> As I understood it, you responded that using the lts.conf from the
> correct tftp directory fixed the issue.
>
> Is this new bug a different issue somehow?
>
>
> live well,
> vagrant
>

Fixes pushed to git:

https://git.launchpad.net/ltsp/commit/?id=820edfb17e75f19072293a2a418a021a54f1e614
https://git.launchpad.net/ltsp/commit/?id=c55e15701aa660efb2aad034a1976b4eaf641f5d

fixed in 5.5.10