On Friday, October 12, 2018 at 7:15:49 AM UTC-7, Phil Green wrote:
>
> I have discovered that when I installed the rtc I forgot to remove the
> fake-clock service.
>
>
Yup - that'll do it all the time.
--
You received this message because you are subscribed to the Google Groups
"weewx-user"
Thanks for the advice.
I have discovered that when I installed the rtc I forgot to remove the
fake-clock service.
That is why my time was in the past until the rtc was read at startup.
I have re-enabled Weewx to auto start and restarted the Pi and all is fine now.
Phil.
--
You received
One point... if you are on a recent OS and using systemd, part of the
advertising for it is faster startup by paralleling things at startup.
Another feature of the service files is the ability to have one service
wait for another to get going. In this case, you'd want the weewx.service
to
On Friday, October 12, 2018 at 9:12:03 AM UTC+1, gjr80 wrote:
>
> There have been at least a couple of mechanisms used. Previously (since
> v3.4.0) on startup WeeWX would wait for a system clock that was after 1
> January 2000. More recently (since v3.8.1) on startup WeeWX waits for a
>
There have been at least a couple of mechanisms used. Previously (since v3.4.0)
on startup WeeWX would wait for a system clock that was after 1 January 2000.
More recently (since v3.8.1) on startup WeeWX waits for a system clock that is
later than the creation time of weewx.conf.
Gary
--
You
On Thursday, 11 October 2018 22:50:15 UTC+1, vince wrote:
>
> Recent weewx versions should already delay startup until you get accurate
> system time.
>
Out of interest, how does it do that?
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
On Thursday, October 11, 2018 at 1:51:12 PM UTC-7, Phil Green wrote:
>
> My question, I would like to stop Weewx from auto starting, but still use:-
> sudo /etc/init.d/weewx start
> To start Weewx manually.
The reason I ask is that I have a real-time clock on my system but
> sometimes Weewx
