Taken from [1]: "However, if the difference between the client time and server time is greater than the panic threshold, which defaults to 1000 s, the daemon will send a message to the system log and shut down without setting the clock."
On RTC-less or 'fresh' systems with unpredicatble inital date ntpd will stop with work undone (note: I did NOT find the message mentioned above - so it took long way to fix). This is a wide use case for using NTP in production: No need for initial datetime setup by some operator. [1] http://doc.ntp.org/4.1.1/debug.htm Signed-off-by: Andreas Müller <[email protected]> --- .../recipes-support/ntp/ntp/ntpd.service | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/meta-networking/recipes-support/ntp/ntp/ntpd.service b/meta-networking/recipes-support/ntp/ntp/ntpd.service index bd87b1e..eb9c030 100644 --- a/meta-networking/recipes-support/ntp/ntp/ntpd.service +++ b/meta-networking/recipes-support/ntp/ntp/ntpd.service @@ -5,7 +5,7 @@ After=network.target [Service] Type=forking PIDFile=/run/ntpd.pid -ExecStart=/usr/bin/ntpd -p /run/ntpd.pid +ExecStart=/usr/bin/ntpd -p /run/ntpd.pid -g [Install] WantedBy=multi-user.target -- 1.7.6.5 _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
