Date: Wed, 27 Mar 2024 13:09:43 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: Nuno Teixeira <eduardo@freebsd.org> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org> Subject: Re: local/etc/rc.d service that runs before date being set by ntpd Message-ID: <352178670.7273.1711541383408@localhost> In-Reply-To: <CAFDf7UKeB8VB%2B0soZDzm8j_%2BS=sjsR5957tqxk1TXS6-7HQU2w@mail.gmail.com> References: <CAFDf7UKeB8VB%2B0soZDzm8j_%2BS=sjsR5957tqxk1TXS6-7HQU2w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_7272_1355329237.1711541383387 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Nuno Teixeira <eduardo@freebsd.org> Datum: woensdag, 27 maart 2024 10:55 Aan: FreeBSD ARM List <freebsd-arm@freebsd.org> Onderwerp: local/etc/rc.d service that runs before date being set by ntpd > > Hello all, > > On rpi4 I use a service dns/noip and found that it don't get actual date from ntpd: > > /var/log/daemon.log (today) after boot > --- > <snip> > Mar 27 09:09:40 rpi4 dhclient[1183]: DHCPREQUEST on genet0 to 192.168.1.1 port 67 > Mar 27 09:09:40 rpi4 dhclient[1183]: DHCPACK from 192.168.1.1 > Mar 27 09:09:40 rpi4 dhclient[1183]: bound to 192.168.1.66 -- renewal in 1800 seconds. > Jan 1 01:00:34 rpi4 noip2[1617]: v2.1.9 daemon started with NAT enabled > Jan 1 01:00:35 rpi4 noip2[1617]: freebsdrpi4.hopto.org was already set to 149.90.156.215. > <service noip restart> > Mar 27 09:26:13 rpi4 noip2[1617]: v2.1.9 daemon ended. > Mar 27 09:26:13 rpi4 noip2[1887]: v2.1.9 daemon started with NAT enabled > Mar 27 09:26:14 rpi4 noip2[1887]: freebsdrpi4.hopto.org was already set to 149.90.156.215. > --- > rcconf: > ntpd_enable="YES" > ntpd_sync_on_start="YES" > > Checking `rcorder /etc/rc.d/* /usr/local/etc/rcd/*` have correct order (?): > > <snip> > /etc/rc.d/ntpdate > ... > /etc/rc.d/sdpd > /etc/rc.d/rarpd > /etc/rc.d/powerd > /etc/rc.d/ntpd > /etc/rc.d/nscd > /usr/local/etc/rc.d/dbus > /usr/local/etc/rc.d/git_daemon > /usr/local/etc/rc.d/noip > /etc/rc.d/rfcomm_pppd_server > /etc/rc.d/mountd > /etc/rc.d/swaplate > ... > Strange that noip doesn't get correct date at boot time. > > Do I missing something? > > Thanks! > > -- > Nuno Teixeira > FreeBSD Committer (ports) Hi, In my rcorder output noip2 comes before ntpd. But I have in rc.conf: ntpdate_enable="YES" ntpd_enable="YES" ntpdate is run more early in the rcorder. I don't know about ntpd_sync_on_start and if that influences the rcorder. I think it is just an option to ntpd. Please try to add ntpdate_enable="YES". BTW: if you run ZFS-on-boot on RPI you can use sysutils/fakertc to get a bit better time at boot. In UFS the time is stored on disk on unmount/shutdown which is used to set the time on startup. ZFS does not have this feature. Fakertc mimics this as good as it can which can help to have a "decent" time to make TLS certificates, etc. valid on boot. Regards, Ronald. ------=_Part_7272_1355329237.1711541383387 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body><br> <p><strong>Van:</strong> Nuno Teixeira <eduardo@freebsd.org><br> <strong>Datum:</strong> woensdag, 27 maart 2024 10:55<br> <strong>Aan:</strong> FreeBSD ARM List <freebsd-arm@freebsd.org><br> <strong>Onderwerp:</strong> local/etc/rc.d service that runs before date being set by ntpd</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="MultipartAlternativeViewer"> <div class="TextHTMLViewer" id="P.P.P"> <div>Hello all,<br> <br> On rpi4 I use a service dns/noip and found that it don't get actual date from ntpd: <div> </div> <div>/var/log/daemon.log (today) after boot</div> <div>---</div> <snip><br> Mar 27 09:09:40 rpi4 dhclient[1183]: DHCPREQUEST on genet0 to 192.168.1.1 port 67<br> Mar 27 09:09:40 rpi4 dhclient[1183]: DHCPACK from 192.168.1.1<br> Mar 27 09:09:40 rpi4 dhclient[1183]: bound to 192.168.1.66 -- renewal in 1800 seconds.<br> <b>Jan 1 01:00:34</b> rpi4 noip2[1617]: v2.1.9 daemon started with NAT enabled<br> <b>Jan 1 01:00:35</b> rpi4 noip2[1617]: <a href="http://freebsdrpi4.hopto.org">freebsdrpi4.hopto.org</a>; was already set to 149.90.156.215.<br> <service noip restart><br> <b>Mar 27 09:26:13</b> rpi4 noip2[1617]: v2.1.9 daemon ended.<br> Mar 27 09:26:13 rpi4 noip2[1887]: v2.1.9 daemon started with NAT enabled <div>Mar 27 09:26:14 rpi4 noip2[1887]: <a href="http://freebsdrpi4.hopto.org">freebsdrpi4.hopto.org</a>; was already set to 149.90.156.215.</div> <div>---</div> <br> rcconf:<br> ntpd_enable="YES"<br> ntpd_sync_on_start="YES" <div> </div> <div>Checking `rcorder /etc/rc.d/* /usr/local/etc/rcd/*` have correct order (?):</div> <div> </div> <div><snip></div> <div> <pre><b>/etc/rc.d/ntpdate</b> ... /etc/rc.d/sdpd /etc/rc.d/rarpd /etc/rc.d/powerd <b>/etc/rc.d/ntpd</b> /etc/rc.d/nscd /usr/local/etc/rc.d/dbus /usr/local/etc/rc.d/git_daemon <b>/usr/local/etc/rc.d/noip</b> /etc/rc.d/rfcomm_pppd_server /etc/rc.d/mountd /etc/rc.d/swaplate ... </pre> </div> <div>Strange that noip doesn't get correct date at boot time.</div> <div> </div> <div>Do I missing something?</div> <div> </div> <div>Thanks!</div> <div> </div> --<br> Nuno Teixeira<br> FreeBSD Committer (ports)</div> </div> </div> </div> </blockquote> <br> <br> Hi,<br> <br> In my rcorder output noip2 comes before ntpd.<br> But I have in rc.conf:<br> ntpdate_enable="YES"<br> ntpd_enable="YES"<br> <br> ntpdate is run more early in the rcorder.<br> <br> I don't know about ntpd_sync_on_start and if that influences the rcorder. I think it is just an option to ntpd.<br> <br> Please try to add ntpdate_enable="YES".<br> <br> BTW: if you run ZFS-on-boot on RPI you can use sysutils/fakertc to get a bit better time at boot. In UFS the time is stored on disk on unmount/shutdown which is used to set the time on startup. ZFS does not have this feature. Fakertc mimics this as good as it can which can help to have a "decent" time to make TLS certificates, etc. valid on boot.<br> <br> Regards,<br> Ronald.<br> </body></html> ------=_Part_7272_1355329237.1711541383387--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?352178670.7273.1711541383408>