a minute is still too long really as weewx attempts a catchup process when
it starts before resuming normal service - and needs the correct time in
order to correctly retrieve any catch up records, set station clock etc etc
- so although you may have 5 minutes until the first archive record is
saved there may be processing taking place before that.
On Tuesday, 11 June 2019 10:21:12 UTC+3, Tolip Wen wrote:
>
> I don't know if this will help but;
>
> I start ntpd with the "-g" switch. This causes it to just set the clock
> from server when it first starts.
> My thinking is that after any power on/reboot situation I don't care if it
> jumps ahead a lot at one time.
>
> I run weewx reports every 5 minutes so I still have to wait for new data,
> but my system clock is correct within a minute of boot.
>
> # Start ntpd:
> ntpd_start() {
> echo -n "Starting NTP daemon: /usr/sbin/ntpd -g -u ntp:ntp"
> /usr/sbin/ntpd -g -u ntp:ntp
> echo
> }
>
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/9e74d731-c9f7-4968-9697-5be0772e1566%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
