ntpd is started early because there are services that work better with
accurate time. In most cases, ntpd will very quickly build accurate clock,
and those services run better.
In some cases, people build situations which challenge ntpd's fast startup.
Especially broken networks.
Because this can happen, ntpd contains code which kind of retries DNS to IP
translations.
It seems to work for me, in the situations where I build semi-broken networks.
I never delete lines in the stock ntpd.conf. I only add additional lines.
ue...@danwin1210.de wrote:
> How can I reload date from ntpd after boot?
> And how can I do it automatically after dnscrypt_proxy service started
> Port: dnscrypt-proxy
> fp$ date
> Wed Dec 22 08:10:38 CET 2021
> fp$ doas rcctl restart ntpd
> ntpd(ok)
> ntpd(ok)
> fp$ date
> Wed Dec 22 08:10:48 CET 2021
>
> I want to reload time from ntpd after dnscrypt_proxy is started because
> it's local DNS server and when it's not started ntpd can't resolve
> hostnames.
>
> fp$ cat /etc/resolv.conf
> nameserver 127.0.0.1
>
> fp$ doas rcctl order ntpd dnscrypt_proxy
> rcctl: ntpd is not a pkg script
> fp$ doas rcctl order dnscrypt_proxy ntpd
> rcctl: ntpd is not a pkg script
>
>
> fp$ cat /etc/rc.d/dnscrypt_proxy
> #!/bin/ksh
> #
> # $OpenBSD: dnscrypt_proxy.rc,v 1.5 2018/10/16 14:55:02 bket Exp $
>
> daemon="/usr/local/bin/dnscrypt-proxy"
> daemon_flags="-config /etc/dnscrypt-proxy.toml"
>
> . /etc/rc.d/rc.subr
>
> pexp="${daemon}${daemon_flags:+ ${daemon_flags}}.*"
>
> rc_bg=YES
> rc_reload=NO
>
> rc_cmd $1
>
>
>
