[ roman.me...@gismap.ch, 2021-04-27 ]
> > On 04/27/2021 11:36 AM Wolfgang Schweer wrote:
> > [ roman.me...@gismap.ch, 2021-04-27 ]
> > > However, I noticed that the value of FAT_RAM_THRESHOLD is ignored. All
> > > devices whether they have more or less than 1000KB of RAM boot as
> > > "thin clie
Hi Wolfgang,
> On 04/27/2021 11:36 AM Wolfgang Schweer wrote:
>
>
> Hi Roman,
>
> [ roman.me...@gismap.ch, 2021-04-27 ]
> > However, I noticed that the value of FAT_RAM_THRESHOLD is ignored. All
> > devices whether they have more or less than 1000KB of RAM boot as
> > "thin client". Somehow
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-27 ]
> However, I noticed that the value of FAT_RAM_THRESHOLD is ignored. All
> devices whether they have more or less than 1000KB of RAM boot as
> "thin client". Somehow it's acting like setting
> LTSP_FATCLIENT="False". The threshold value was workin
Hi Wolfgang,
Yep, this worked, thanks!
However, I noticed that the value of FAT_RAM_THRESHOLD is ignored. All devices
whether they have more or less than 1000KB of RAM boot as "thin client".
Somehow it's acting like setting LTSP_FATCLIENT="False". The threshold value
was working well for me in
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-24 ]
> I still have an issue with "FAT_RAM_THRESHOLD=1000" in
> "/var/lib/tftpboot/ltsp/i386/lts.conf".
No idea why it doesn't take effect.
Edit /opt/ltsp/i386/etc/lts.conf instead and run 'ltsp-update-image'
before starting an LTSP client.
Wolfgang
uot;. This is weird to me and I don't think I have seen this
before.
Any ideas why?
Kind regards,
Roman
> -- Original Message --
> From: roman.me...@gismap.ch
> To: Wolfgang Schweer , debian-edu@lists.debian.org
> Date: 04/23/2021 2:53 PM
> Subject: Re: Client
Hi Wolfgang,
I tried using iburst as you suggested. It seems not to sync anymore.
Anyway, I'll do more tests and if I find something I'll post my findings.
Kind regards,
Roman
> On 04/23/2021 3:31 PM Wolfgang Schweer wrote:
>
>
> Hi Roman,
>
> [ roman.me...@gismap.ch, 2021-04-23 ]
> > I ha
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-23 ]
> I have done a new installation this morning using the
> i386-server-image instead of the amd64 one. Things definitely work
> much better now.
Good to hear.
> Client time sync without internet was not working for me with the
> default setting
Hi Wolfgang,
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 "ltsp
Hi Roman,
[ roman.me...@gismap.ch, 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 ar
Hi Wolfgang,
I have new findings which may help to narrow things down hopefully.
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 c
[ roman.me...@gismap.ch, 2021-04-21 ]
> 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
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"
l
Hi Roman,
[ roman.me...@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
Hi Wolfgang,
Well, I had to create the i386 image myself because it is not created by
default any longer.
I also played around with LDAP unsuccessfully trying to increasing the
threshold for my clients to boot as thin client.
That's all I can remember. Is the log file I sent not helpful?
Kind
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-21 ]
> I just checked the content of /etc/ntp.conf of my "diskless
> workstation" client. No line "server ntp" has been appended.
>
> Guess that explains the problem I'm having, right?
Yes; any LDAP or LTSP chroot changes on your side?
Wolfgang
sig
-- Original Message --
> From: roman.me...@gismap.ch
> To: Wolfgang Schweer , "debian-edu@lists.debian.org"
>
> Date: 04/21/2021 10:33 AM
> Subject: Re: Client time/date synchronisation
>
>
> Hi Wolfgang,
>
> I just checked the content o
Hi Wolfgang,
I just checked the content of /etc/ntp.conf of my "diskless workstation"
client. No line "server ntp" has been appended.
Guess that explains the problem I'm having, right?
Kind regards,
Roman
> On 04/20/2021 5:28 PM Wolfgang Schweer wrote:
>
>
> Hi Roman,
>
> [ roman.me...@gi
Hi Roman,
[ roman.me...@gismap.ch, 2021-04-20 ]
> Fact is that my LTSP clients don't have the correct time if the server
> has no internet connection, which may be perfectly normal, right?
No, it should work.
> There's none on the client in /opt/ltsp/i386/etc/ntp.conf though.
LTSP modifies th
Hi Wolfgang,
I'm not sure I fully understand the content of the file you sent.
Fact is that my LTSP clients don't have the correct time if the server has no
internet connection, which may be perfectly normal, right?
Kind regards,
Roman
> On 04/20/2021 12:13 PM Wolfgang Schweer wrote:
>
>
>
LTSP switched to systemd-timesyncd, configuration is done in LDAP, see:
https://salsa.debian.org/debian-edu/debian-edu-config/-/blob/buster/cf3/cf.ntp
Wolfgang
(sent from mobile device)
Am April 20, 2021 9:30:47 AM UTC schrieb roman.me...@gismap.ch:
>Hi Petter,
>
>I found a server line on the s
Hi Petter,
I found a server line on the server, which is:
server 127.127.1.0
There's none on the client in /opt/ltsp/i386/etc/ntp.conf though.
Kind regards,
Roman
> On 04/20/2021 10:02 AM Petter Reinholdtsen wrote:
>
>
> [Roman Meier]
> > Is there another way to synchronize the time e.g. wi
[Roman Meier]
> Is there another way to synchronize the time e.g. with the server
> instead of the internet?
In earlier times, all clients had their /etc/ntp.conf file set up to
synchronise their clocks with the server, for just this kind of
scenario. Is this no longer the case?
Look for the 'se
Hi folks,
Many of our clients have set the wrong time/date in the bios mostly as a result
of issues with old cmos batteries.
When the server is connected to the internet the time/date is automatically
corrected and things work just fine. However, most of the time internet access
is off. Then t
24 matches
Mail list logo
