Re: Client time/date synchronisation
I have done a new installation this morning using the i386-server-image instead of the amd64 one. Things definitely work much better now.
Client time sync without internet was not working for me with the default setting "ltspConfig: TIMESERVER=ntp". You suggested to switch to "ltspConfig: TIMESERVER=auto". This works for me appending "server 10.0.2.2" to /etc/ntp.conf. Syncing however happens with several minutes delay.
Thin client is also working using "ltspConfig: LTSP_FATCLIENT="False"". However, this setting is not what I prefer because it deactivates the possibility to boot as "diskless workstation" in the "primary subnet".
Removing "ltspConfig: LTSP_FATCLIENT="False"" and adding "ltspConfig: FAT_RAM_THRESHOLD=1000" should work but doesn't for me. I don't know why.
The fix for me was to remove "ltspConfig: LTSP_FATCLIENT="False"" again and editing the configuration in /var/lib/tftpboot/ltsp/i386/lts.conf by adding "FAT_RAM_THRESHOLD=1000".
Thanks a lot for your help fixing my issues.
> On 04/22/2021 2:52 PM Wolfgang Schweer <firstname.lastname@example.org> wrote:
> Hi Roman,
> [ email@example.com, 2021-04-22 ]
> > This morning I decided to switch back to the original amd64 image and
> > testing with a newer client device I just got.
> > The good news is that everything seems to work just fine. The device
> > is booting nicely as thin client. LDAP settings are added as expected
> > to /run/ltsp/ltsp_config_env and there's a new entry "server ntp" at
> > the end of /etc/ntp.conf.
> > These things are not happening when I boot using the i386 image.
> > More ideas why this is happening?
> Might be due to the 64-bit/32-bit mix. I don't have a test environment
> to check it, though.
> As another option to get the Toughbooks working, you could install the
> combined server using the 32-bit BD ISO image, see the status page:
> The LTSP chroot will be 32-bit (i386) by default in this case (so no
> $arch mix) and things should work also for 64-bit clients.