Re: Client time/date synchronisation

[roman.meier@gismap.ch]

Hi Wolfgang,

Sorry, still no good news.

I have added the suggested line to LDAP. It looks like this now:

121 cn=ltspConfigDefault,ou=ltsp,dc=skole,dc=skolelinux,dc=no
objectClass: ltspClientConfig
cn: ltspConfigDefault
ltspConfig: KEEP_SYSTEM_SERVICES=lightdm
ltspConfig: LTSP_FATCLIENT="False"
ltspConfig: TIMESERVER=ntp

After this, my client still boots as "diskless workstation" and the content of /run/ltsp/ltsp_config_env shows LTSP_FATCLIENT="True" instead of "False".

Are changes to LDAP validated on-the-fly upon save or do I need to add another step like commit, rebuilding the image, etc.?

Kind regards,
Roman

> On 04/21/2021 1:31 PM Wolfgang Schweer <w.schweer@gmx.de> wrote:
> 
>  
> Hi Roman,
> 
> [ roman.meier@gismap.ch, 2021-04-21 ]
> > I also played around with LDAP unsuccessfully trying to increasing the 
> > threshold for my clients to boot as thin client.
> 
> Maybe it doesn't take effect anymore for some reason…
> But you should be able to do this by setting the client type in LDAP
> 
> ltspConfig: LTSP_FATCLIENT="False"
> 
> You should be able to see the environment variables actually used:
> cat /run/ltsp/ltsp_config_env (diskless workstation)
> 
> If running a thin client, log in graphically as first user. Then switch 
> to a terminal (Ctrl-Alt-F1), log in as first user, run 'sudo su -' to 
> become root and run 'cat /run/ltsp/ltsp_config_env' and maybe check 
> other things, too.
>  
> > That's all I can remember. Is the log file I sent not helpful?
> 
> I can't find anything suspicious… 
> 
> Wolfgang