Skip to contentSkip to conversation

package/ntp: sntp time sync script

PATCH Superseded Matt Weber 4 participants 9 messages Dec 12, 2018 – Feb 4, 2019

lore
Share & tools
lore

Matt Weber

author
#0 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

This patch adds the installation of a startup script if the sntp utility is selected as an option. The utility is design to do a one time step/slew adjustment of the system time (similar to the ntpdate tool http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate).
One nice benefit over ntpdate is that sntp can run while ntpd is still running. However, ntpd may still need to be restarted if the time step was large enough.

The script provides the ability to override the arguments as part of a /etc/defaults/sntp file.

On a local LAN, the initial large step adjustment took less then one second to be retrieved and system time updated. If a user already has a RTC maintaining the time and the system was powered off for a long period of time, the script assumes a slew adjustment when +/- 128ms, rather then a time step(jump). This could be further tuned by a user with the /etc/defaults/sntp configuration file.

One NTP pool server is being set as sntp uses all of the servers provided when the DNS is resolved as servers to attempt to retrieve time from before timing out. It looks like currently that is 4 servers per *pool.ntp.org hostname.

Cc Oscar Gomez Fuente <[email protected]>

---
Changes
v4 -> v5
- Fixed permissions on S48sntp and S49ntp scripts

[Arnout
- Updated script to follow Carlos's recently merged syslog script refresh
- Added kconfig help comment about the script
- Added notes in S49sntp about behavior of the tool
- shellcheck fixes
- Moved touch of key database file into start function

v3 -> v4
- Updated S48sntp script to just use a single pool host which provides 4 NTP servers sntp will query before timing out

v2 -> v3
- Moved initial time set to a S48sntp script as originally suggested by Oscar and preferred by Arnout
- Switched to sntp tool as it simplified the logic around when and how do we call the tool to perform this time sync (it handles when to slew/step and multiple servers at once)

v1 -> v2
[Arnout
- Moved NTP_WAIT_DELAY above sourcing of configuration file
- Switched to using unix time for current time check
- Added comment on why redirection of stdout and stderr
- Attempted to use the pid file but found it added more calls to the shell then using a variable, so switched back
- Adjusted printout so the actual ntpd service start was aligned with the respecting Ok/Fail.
- Dropped -g from the main service call as the "big" time jump should have already occurred with the one-shot ntpd -gq.

v1
Based on Oscar's v1 patch to add a ntpdate startup script.
http://patchwork.ozlabs.org/patch/986852/

---
 package/ntp/Config.in |  7 ++++++-
 package/ntp/S48sntp   | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
 package/ntp/S49ntp    |  0
 package/ntp/ntp.mk    |  9 +++++++++
 4 files changed, 70 insertions(+), 1 deletion(-)
 create mode 100644 package/ntp/S48sntp
 mode change 100755 => 100644 package/ntp/S49ntp
package/ntp/Config.in +6 -1
index efd47e1..97d933b 100644
@@ -12,7 +12,12 @@ if BR2_PACKAGE_NTP
 config BR2_PACKAGE_NTP_SNTP
 	bool "sntp"
 	help
-	  Simple network time protocol program
+	  Simple network time protocol program (a replacement
+	  for the ntpdate tool)
+
+	  A script is installed as S48sntp which will retrieve and
+	  step the time if there is a large difference before ntpd
+	  takes over the necessary slew adjustments in S49ntp.
 
 config BR2_PACKAGE_NTP_NTP_KEYGEN
 	bool "ntp-keygen"
package/ntp/S48sntp new file +55 -0

55 lines not on this page · raw message

package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644
package/ntp/ntp.mk +9 -0
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
 	$(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+	$(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
 	$(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+	$(NTP_INSTALL_INIT_SYSV_SNTP)
 endef
 
 define NTP_INSTALL_INIT_SYSTEMD
Signature · 1 line
1.9.1
#1 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

Arnout / Oscar,

Quoted 19 lines · Matt Weber

This patch adds the installation of a startup script if the sntp utility is selected as an option. The utility is design to do a one time step/slew adjustment of the system time (similar to the ntpdate tool http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate).
One nice benefit over ntpdate is that sntp can run while ntpd is still running. However, ntpd may still need to be restarted if the time step was large enough.

The script provides the ability to override the arguments as part of a /etc/defaults/sntp file.

On a local LAN, the initial large step adjustment took less then one second to be retrieved and system time updated. If a user already has a RTC maintaining the time and the system was powered off for a long period of time, the script assumes a slew adjustment when +/- 128ms, rather then a time step(jump). This could be further tuned by a user with the /etc/defaults/sntp configuration file.

Quoted 7 lines

One NTP pool server is being set as sntp uses all of the servers provided when the DNS is resolved as servers to attempt to retrieve time from before timing out. It looks like currently that is 4 servers per *pool.ntp.org hostname.

Cc Oscar Gomez Fuente <[email protected]>

Arnout, merge? Oscar tested the v4 before I did the changes for Carlos's style of script so I didn't carry over his reviewed-by as enough was touched....

Quoted 156 lines

---
Changes
v4 -> v5
- Fixed permissions on S48sntp and S49ntp scripts

[Arnout
- Updated script to follow Carlos's recently merged syslog script refresh
- Added kconfig help comment about the script
- Added notes in S49sntp about behavior of the tool
- shellcheck fixes
- Moved touch of key database file into start function

v3 -> v4
- Updated S48sntp script to just use a single pool host which provides 4 NTP servers sntp will query before timing out

v2 -> v3
- Moved initial time set to a S48sntp script as originally suggested by Oscar and preferred by Arnout
- Switched to sntp tool as it simplified the logic around when and how do we call the tool to perform this time sync (it handles when to slew/step and multiple servers at once)

v1 -> v2
[Arnout
- Moved NTP_WAIT_DELAY above sourcing of configuration file
- Switched to using unix time for current time check
- Added comment on why redirection of stdout and stderr
- Attempted to use the pid file but found it added more calls to the shell then using a variable, so switched back
- Adjusted printout so the actual ntpd service start was aligned with the respecting Ok/Fail.
- Dropped -g from the main service call as the "big" time jump should have already occurred with the one-shot ntpd -gq.

v1
Based on Oscar's v1 patch to add a ntpdate startup script.
http://patchwork.ozlabs.org/patch/986852/

---
 package/ntp/Config.in |  7 ++++++-
 package/ntp/S48sntp   | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
 package/ntp/S49ntp    |  0
 package/ntp/ntp.mk    |  9 +++++++++
 4 files changed, 70 insertions(+), 1 deletion(-)
 create mode 100644 package/ntp/S48sntp
 mode change 100755 => 100644 package/ntp/S49ntp
package/ntp/Config.in +6 -1
index efd47e1..97d933b 100644
@@ -12,7 +12,12 @@ if BR2_PACKAGE_NTP
 config BR2_PACKAGE_NTP_SNTP
        bool "sntp"
        help
-         Simple network time protocol program
+         Simple network time protocol program (a replacement
+         for the ntpdate tool)
+
+         A script is installed as S48sntp which will retrieve and
+         step the time if there is a large difference before ntpd
+         takes over the necessary slew adjustments in S49ntp.
 
 config BR2_PACKAGE_NTP_NTP_KEYGEN
        bool "ntp-keygen"
package/ntp/S48sntp new file +55 -0
new file mode 100644
index 0000000..96d8d50
@@ -0,0 +1,55 @@
+#!/bin/sh
+
+DAEMON="sntp"
+# sntp uses all the IPs resolved for the hostname (i.e. pool.ntp.org has 4).
+# It will try each until they either all timeout or time has been set. Thus
+# default to only providing one NTP pool host.
+SNTP_SERVERS="pool.ntp.org"
+# Step if time delta is greater then 128ms, otherwise slew
+SNTP_ARGS="-Ss -M 128"
+SNTP_KEY_CACHE="/tmp/kod"
+
+# shellcheck source=/dev/null
+[ -r "/etc/default/$DAEMON" ] && . "/etc/default/$DAEMON"
+
+start() {
+       printf 'Starting %s: ' "$DAEMON"
+       # Create key cache file to prevents warning that file is missing
+       touch $SNTP_KEY_CACHE
+       # shellcheck disable=SC2086 # we need the word splitting
+       /usr/bin/$DAEMON $SNTP_ARGS -K $SNTP_KEY_CACHE $SNTP_SERVERS
+       # sntp behavior
+       # - Does not background
+       # - Does not infinitely block
+       # - Time-out w/o network = ~2 sec
+       # - Time-out w/ network = ~5sec * # of servers
+       status=$?
+       if [ "$status" -eq 0 ]; then
+               echo "OK"
+       else
+               echo "FAIL"
+       fi
+       return "$status"
+}
+
+stop() {
+       echo "Nothing to do, $DAEMON is not a daemon."
+}
+
+restart() {
+       stop
+       sleep 1
+       start
+}
+
+reload() {
+       echo "Nothing to do, $DAEMON does not support reload."
+}
+
+case "$1" in
+       start|stop|restart|reload)
+               "$1";;
+       *)
+               echo "Usage: $0 {start|stop|restart|reload}"
+               exit 1
+esac
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644
package/ntp/ntp.mk +9 -1
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
        $(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+       $(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
        $(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+       $(NTP_INSTALL_INIT_SYSV_SNTP)
 endef
 
 define NTP_INSTALL_INIT_SYSTEMD
--

1.9.1

#2 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

Hi everyone,

Do you want me to check again on my raspberry pi 3B+?

Best regards.

Oscar Gomez Fuente
TST Sistemas
www.tst-sistemas.es

?scar G?mez Fuente
Electronic Engineer & Degree in Physical Sciences
Mobile: 659.28.97.90
Email: oscargomezf at gmail.com
Website: www.oscargomezf.com

Quoted 193 lines · Matthew Weber

Arnout / Oscar,

Quoted 19 lines · Matt Weber

This patch adds the installation of a startup script if the sntp utility is selected as an option. The utility is design to do a one time step/slew adjustment of the system time (similar to the ntpdate tool http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate).
One nice benefit over ntpdate is that sntp can run while ntpd is still running. However, ntpd may still need to be restarted if the time step was large enough.

The script provides the ability to override the arguments as part of a /etc/defaults/sntp file.

On a local LAN, the initial large step adjustment took less then one second to be retrieved and system time updated. If a user already has a RTC maintaining the time and the system was powered off for a long period of time, the script assumes a slew adjustment when +/- 128ms, rather then a time step(jump). This could be further tuned by a user with the /etc/defaults/sntp configuration file.

Quoted 7 lines

One NTP pool server is being set as sntp uses all of the servers provided when the DNS is resolved as servers to attempt to retrieve time from before timing out. It looks like currently that is 4 servers per *pool.ntp.org hostname.

Cc Oscar Gomez Fuente <[email protected]>

Arnout, merge? Oscar tested the v4 before I did the changes for Carlos's style of script so I didn't carry over his reviewed-by as enough was touched....

Quoted 156 lines

---
Changes
v4 -> v5
- Fixed permissions on S48sntp and S49ntp scripts

[Arnout
- Updated script to follow Carlos's recently merged syslog script refresh
- Added kconfig help comment about the script
- Added notes in S49sntp about behavior of the tool
- shellcheck fixes
- Moved touch of key database file into start function

v3 -> v4
- Updated S48sntp script to just use a single pool host which provides 4 NTP servers sntp will query before timing out

v2 -> v3
- Moved initial time set to a S48sntp script as originally suggested by Oscar and preferred by Arnout
- Switched to sntp tool as it simplified the logic around when and how do we call the tool to perform this time sync (it handles when to slew/step and multiple servers at once)

v1 -> v2
[Arnout
- Moved NTP_WAIT_DELAY above sourcing of configuration file
- Switched to using unix time for current time check
- Added comment on why redirection of stdout and stderr
- Attempted to use the pid file but found it added more calls to the shell then using a variable, so switched back
- Adjusted printout so the actual ntpd service start was aligned with the respecting Ok/Fail.
- Dropped -g from the main service call as the "big" time jump should have already occurred with the one-shot ntpd -gq.

v1
Based on Oscar's v1 patch to add a ntpdate startup script.
http://patchwork.ozlabs.org/patch/986852/

---
 package/ntp/Config.in |  7 ++++++-
 package/ntp/S48sntp   | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
 package/ntp/S49ntp    |  0
 package/ntp/ntp.mk    |  9 +++++++++
 4 files changed, 70 insertions(+), 1 deletion(-)
 create mode 100644 package/ntp/S48sntp
 mode change 100755 => 100644 package/ntp/S49ntp
package/ntp/Config.in +6 -1
index efd47e1..97d933b 100644
@@ -12,7 +12,12 @@ if BR2_PACKAGE_NTP
 config BR2_PACKAGE_NTP_SNTP
        bool "sntp"
        help
-         Simple network time protocol program
+         Simple network time protocol program (a replacement
+         for the ntpdate tool)
+
+         A script is installed as S48sntp which will retrieve and
+         step the time if there is a large difference before ntpd
+         takes over the necessary slew adjustments in S49ntp.
 
 config BR2_PACKAGE_NTP_NTP_KEYGEN
        bool "ntp-keygen"
package/ntp/S48sntp new file +55 -0
new file mode 100644
index 0000000..96d8d50
@@ -0,0 +1,55 @@
+#!/bin/sh
+
+DAEMON="sntp"
+# sntp uses all the IPs resolved for the hostname (i.e. pool.ntp.org has 4).
+# It will try each until they either all timeout or time has been set. Thus
+# default to only providing one NTP pool host.
+SNTP_SERVERS="pool.ntp.org"
+# Step if time delta is greater then 128ms, otherwise slew
+SNTP_ARGS="-Ss -M 128"
+SNTP_KEY_CACHE="/tmp/kod"
+
+# shellcheck source=/dev/null
+[ -r "/etc/default/$DAEMON" ] && . "/etc/default/$DAEMON"
+
+start() {
+       printf 'Starting %s: ' "$DAEMON"
+       # Create key cache file to prevents warning that file is missing
+       touch $SNTP_KEY_CACHE
+       # shellcheck disable=SC2086 # we need the word splitting
+       /usr/bin/$DAEMON $SNTP_ARGS -K $SNTP_KEY_CACHE $SNTP_SERVERS
+       # sntp behavior
+       # - Does not background
+       # - Does not infinitely block
+       # - Time-out w/o network = ~2 sec
+       # - Time-out w/ network = ~5sec * # of servers
+       status=$?
+       if [ "$status" -eq 0 ]; then
+               echo "OK"
+       else
+               echo "FAIL"
+       fi
+       return "$status"
+}
+
+stop() {
+       echo "Nothing to do, $DAEMON is not a daemon."
+}
+
+restart() {
+       stop
+       sleep 1
+       start
+}
+
+reload() {
+       echo "Nothing to do, $DAEMON does not support reload."
+}
+
+case "$1" in
+       start|stop|restart|reload)
+               "$1";;
+       *)
+               echo "Usage: $0 {start|stop|restart|reload}"
+               exit 1
+esac
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644
package/ntp/ntp.mk +9 -1
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
        $(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+       $(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
        $(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+       $(NTP_INSTALL_INIT_SYSV_SNTP)
 endef
 
 define NTP_INSTALL_INIT_SYSTEMD
--

1.9.1

#3 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

?scar G?mez Fuente
Electronic Engineer & Degree in Physical Sciences
Mobile: 659.28.97.90
Email: oscargomezf at gmail.com
Website: www.oscargomezf.com

Quoted 213 lines · Oscar Gomez Fuente

Hi everyone,

Do you want me to check again on my raspberry pi 3B+?

Best regards.

Oscar Gomez Fuente
TST Sistemas
www.tst-sistemas.es

?scar G?mez Fuente
Electronic Engineer & Degree in Physical Sciences
Mobile: 659.28.97.90
Email: oscargomezf at gmail.com
Website: www.oscargomezf.com

Quoted 193 lines · Matthew Weber

Arnout / Oscar,

Quoted 19 lines · Matt Weber

This patch adds the installation of a startup script if the sntp utility is selected as an option. The utility is design to do a one time step/slew adjustment of the system time (similar to the ntpdate tool http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate).
One nice benefit over ntpdate is that sntp can run while ntpd is still running. However, ntpd may still need to be restarted if the time step was large enough.

The script provides the ability to override the arguments as part of a /etc/defaults/sntp file.

On a local LAN, the initial large step adjustment took less then one second to be retrieved and system time updated. If a user already has a RTC maintaining the time and the system was powered off for a long period of time, the script assumes a slew adjustment when +/- 128ms, rather then a time step(jump). This could be further tuned by a user with the /etc/defaults/sntp configuration file.

Quoted 7 lines

One NTP pool server is being set as sntp uses all of the servers provided when the DNS is resolved as servers to attempt to retrieve time from before timing out. It looks like currently that is 4 servers per *pool.ntp.org hostname.

Cc Oscar Gomez Fuente <[email protected]>

Arnout, merge? Oscar tested the v4 before I did the changes for Carlos's style of script so I didn't carry over his reviewed-by as enough was touched....

Quoted 156 lines

---
Changes
v4 -> v5
- Fixed permissions on S48sntp and S49ntp scripts

[Arnout
- Updated script to follow Carlos's recently merged syslog script refresh
- Added kconfig help comment about the script
- Added notes in S49sntp about behavior of the tool
- shellcheck fixes
- Moved touch of key database file into start function

v3 -> v4
- Updated S48sntp script to just use a single pool host which provides 4 NTP servers sntp will query before timing out

v2 -> v3
- Moved initial time set to a S48sntp script as originally suggested by Oscar and preferred by Arnout
- Switched to sntp tool as it simplified the logic around when and how do we call the tool to perform this time sync (it handles when to slew/step and multiple servers at once)

v1 -> v2
[Arnout
- Moved NTP_WAIT_DELAY above sourcing of configuration file
- Switched to using unix time for current time check
- Added comment on why redirection of stdout and stderr
- Attempted to use the pid file but found it added more calls to the shell then using a variable, so switched back
- Adjusted printout so the actual ntpd service start was aligned with the respecting Ok/Fail.
- Dropped -g from the main service call as the "big" time jump should have already occurred with the one-shot ntpd -gq.

v1
Based on Oscar's v1 patch to add a ntpdate startup script.
http://patchwork.ozlabs.org/patch/986852/

---
 package/ntp/Config.in |  7 ++++++-
 package/ntp/S48sntp   | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++
 package/ntp/S49ntp    |  0
 package/ntp/ntp.mk    |  9 +++++++++
 4 files changed, 70 insertions(+), 1 deletion(-)
 create mode 100644 package/ntp/S48sntp
 mode change 100755 => 100644 package/ntp/S49ntp
package/ntp/Config.in +6 -1
index efd47e1..97d933b 100644
@@ -12,7 +12,12 @@ if BR2_PACKAGE_NTP
 config BR2_PACKAGE_NTP_SNTP
        bool "sntp"
        help
-         Simple network time protocol program
+         Simple network time protocol program (a replacement
+         for the ntpdate tool)
+
+         A script is installed as S48sntp which will retrieve and
+         step the time if there is a large difference before ntpd
+         takes over the necessary slew adjustments in S49ntp.
 
 config BR2_PACKAGE_NTP_NTP_KEYGEN
        bool "ntp-keygen"
package/ntp/S48sntp new file +55 -0
new file mode 100644
index 0000000..96d8d50
@@ -0,0 +1,55 @@
+#!/bin/sh
+
+DAEMON="sntp"
+# sntp uses all the IPs resolved for the hostname (i.e. pool.ntp.org has 4).
+# It will try each until they either all timeout or time has been set. Thus
+# default to only providing one NTP pool host.
+SNTP_SERVERS="pool.ntp.org"
+# Step if time delta is greater then 128ms, otherwise slew
+SNTP_ARGS="-Ss -M 128"
+SNTP_KEY_CACHE="/tmp/kod"
+
+# shellcheck source=/dev/null
+[ -r "/etc/default/$DAEMON" ] && . "/etc/default/$DAEMON"
+
+start() {
+       printf 'Starting %s: ' "$DAEMON"
+       # Create key cache file to prevents warning that file is missing
+       touch $SNTP_KEY_CACHE
+       # shellcheck disable=SC2086 # we need the word splitting
+       /usr/bin/$DAEMON $SNTP_ARGS -K $SNTP_KEY_CACHE $SNTP_SERVERS
+       # sntp behavior
+       # - Does not background
+       # - Does not infinitely block
+       # - Time-out w/o network = ~2 sec
+       # - Time-out w/ network = ~5sec * # of servers
+       status=$?
+       if [ "$status" -eq 0 ]; then
+               echo "OK"
+       else
+               echo "FAIL"
+       fi
+       return "$status"
+}
+
+stop() {
+       echo "Nothing to do, $DAEMON is not a daemon."
+}
+
+restart() {
+       stop
+       sleep 1
+       start
+}
+
+reload() {
+       echo "Nothing to do, $DAEMON does not support reload."
+}
+
+case "$1" in
+       start|stop|restart|reload)
+               "$1";;
+       *)
+               echo "Usage: $0 {start|stop|restart|reload}"
+               exit 1
+esac
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644
package/ntp/ntp.mk +9 -1
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
        $(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+       $(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
        $(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+       $(NTP_INSTALL_INIT_SYSV_SNTP)
 endef
 
 define NTP_INSTALL_INIT_SYSTEMD
--

1.9.1

#4 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

In reply to Matt Weber

Hi Matt,

I've finally applied to master since it really is a useful feature and it
works. However, I have a few additional remarks. Also one for Carlos, the init script dude :-)

On 12/12/2018 04:45, Matt Weber wrote:
[snip]

package/ntp/S48sntp line 3

Quoted 3 lines
package/ntp/S48sntp new file +3 -0
+#!/bin/sh
+
+DAEMON="sntp"

Carlos, I'm starting to doubt the usefulness of this DAEMON variable. Other
variables are prefixed by SNTP_, only this one isn't. In other init scripts you started using PROGRAM instead because it isn't actually a daemon.

However, the only reason to make it a variable is to make it easier to copy and
adapt an existing init script. But really, doing a search/replace of that string is not so much work. And you anyway need to review the entire file, e.g. /usr/bin/$DAEMON is used which may not be correct.

So I'd propose to replace DAEMON with a direct reference to the program. What
do you think?

package/ntp/S48sntp line 7

Quoted 4 lines
package/ntp/S48sntp new file +4 -0
+# sntp uses all the IPs resolved for the hostname (i.e. pool.ntp.org has 4).
+# It will try each until they either all timeout or time has been set. Thus
+# default to only providing one NTP pool host.
+SNTP_SERVERS="pool.ntp.org"

I think this was discussed before, but why isn't this

if [ -e /etc/ntpd.conf ]; then
SNTP_SERVERS="$(sed -n
'/^[[:space:]]*server[[:space:]]\+\([^[:space:]]\+\).*$/s//\1/p' /etc/ntpd.conf | head -1)"
else
SNTP_SERVERS="pool.ntp.org"
fi

so the ntpd.conf gets reused by default?

[snip]

package/ntp/S49ntp

Quoted 3 lines
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644

I applied it now, but isn't this an accident?

Quoted 10 lines
package/ntp/ntp.mk +2 -0
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
 	$(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments

package/ntp/ntp.mk define NTP_INSTALL_TARGET_CMDS · line 107

Quoted 10 lines
package/ntp/ntp.mk +7 -0
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+	$(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
 	$(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+	$(NTP_INSTALL_INIT_SYSV_SNTP)

So, the sntp script only gets installed if ntpd is installed. Is that
intentional? Doesn't sound ideal...

Regards,
Arnout

Quoted 4 lines
package/ntp/ntp.mk +0 -0
 endef
 
 define NTP_INSTALL_INIT_SYSTEMD
#5 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

Arnout,

Quoted 6 lines · Arnout Vandecappelle

Hi Matt,

I've finally applied to master since it really is a useful feature and it
works. However, I have a few additional remarks. Also one for Carlos, the init script dude :-)

:-)

Quoted 2 lines · Matt Weber

[snip]

Quoted 10 lines

package/ntp/S48sntp line 7

Quoted 6 lines
package/ntp/S48sntp new file +4 -0
+# sntp uses all the IPs resolved for the hostname (i.e. pool.ntp.org has 4).
+# It will try each until they either all timeout or time has been set. Thus
+# default to only providing one NTP pool host.
+SNTP_SERVERS="pool.ntp.org"

I think this was discussed before, but why isn't this

if [ -e /etc/ntpd.conf ]; then

Quoted 8 lines
        SNTP_SERVERS="$(sed -n

'/^[[:space:]]*server[[:space:]]\+\([^[:space:]]\+\).*$/s//\1/p' /etc/ntpd.conf | head -1)"
else
SNTP_SERVERS="pool.ntp.org"
fi

so the ntpd.conf gets reused by default?

Definitely could do that. The one thing you have to be careful of is the number of servers you put in that variable as that increases the timeouts for the script to continue (timeout = num servers * num of IPs resolved for each server hostname * timeout per IP). As per the comment above, having one host as default bounds that value.

I just sent a note to the ntp pool guys to check on our status of a buildroot pool. No luck/response so far after I submitted that in Nov 2018.

Quoted 7 lines

[snip]

package/ntp/S49ntp

Quoted 3 lines
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644

I applied it now, but isn't this an accident?

Accident but correct, right? (guessing I wildcarded 644 the folder as part of cleanup) Then the install step correctly places the file and permissions.

Quoted 9 lines
Quoted 9 lines
package/ntp/ntp.mk +0 -0
index af3c1aa..aad1cdd 100644
@@ -93,9 +93,18 @@ define NTP_INSTALL_TARGET_CMDS
      $(INSTALL) -m 644 package/ntp/ntpd.etc.conf $(TARGET_DIR)/etc/ntp.conf
 endef
 
Quoted 15 lines

package/ntp/ntp.mk define NTP_INSTALL_TARGET_CMDS · line 107

Quoted 12 lines
package/ntp/ntp.mk +9 -0
+# This script will step the time if there is a large difference
+# before ntpd takes over the necessary slew adjustments
+ifeq ($(BR2_PACKAGE_NTP_SNTP),y)
+define NTP_INSTALL_INIT_SYSV_SNTP
+     $(INSTALL) -D -m 755 package/ntp/S48sntp $(TARGET_DIR)/etc/init.d/S48sntp
+endef
+endif
+
 ifeq ($(BR2_PACKAGE_NTP_NTPD),y)
 define NTP_INSTALL_INIT_SYSV
      $(INSTALL) -D -m 755 package/ntp/S49ntp $(TARGET_DIR)/etc/init.d/S49ntp
+     $(NTP_INSTALL_INIT_SYSV_SNTP)

So, the sntp script only gets installed if ntpd is installed. Is that
intentional? Doesn't sound ideal...

Oh didn't catch that. Yeah, we ideally should make the ntpd script install a seperate define and then keep the NTP_INSTALL_INIT_SYSV clean and just calling the respective NTP_INSTALL_INIT_SYSV_SNTP and NTP_INSTALL_INIT_SYSV_NTPD. I'll send a patch for this.

Thanks for the feedback. Matt

#6 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

Quoted 7 lines · Matthew Weber
Quoted 4 lines

package/ntp/S49ntp

Quoted 3 lines
package/ntp/S49ntp +0 -0
old mode 100755
new mode 100644

I applied it now, but isn't this an accident?

Accident but correct, right? (guessing I wildcarded 644 the folder as part of cleanup) Then the install step correctly places the file and permissions.

Hm, about half of our init scripts are executable and the other half are not...
Not sure what is the best option here. But keeping it consistent is probably better :-)

Regards,
Arnout

#7 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

In reply to Arnout Vandecappelle
Quoted 22 lines

From: "Arnout Vandecappelle" <[email protected]>
To: "Matthew Weber" <[email protected]>, "buildroot" <[email protected]>
Cc: "Oscar Gomez Fuente" <[email protected]>, "Carlos Santos" <[email protected]>
Sent: Domingo, 3 de fevereiro de 2019 18:00:33
Subject: Re: [Buildroot] [PATCH v5] package/ntp: sntp time sync script

Hi Matt,

I've finally applied to master since it really is a useful feature and it works. However, I have a few additional remarks. Also one for Carlos, the init script dude :-)

On 12/12/2018 04:45, Matt Weber wrote:
[snip]

package/ntp/S48sntp line 3

Quoted 3 lines
package/ntp/S48sntp new file +3 -0
+#!/bin/sh
+
+DAEMON="sntp"

Carlos, I'm starting to doubt the usefulness of this DAEMON variable. Other variables are prefixed by SNTP_, only this one isn't. In other init scripts you started using PROGRAM instead because it isn't actually a daemon.

Quoted 7 lines

However, the only reason to make it a variable is to make it easier to copy and adapt an existing init script. But really, doing a search/replace of that string is not so much work. And you anyway need to review the entire file, e.g. /usr/bin/$DAEMON is used which may not be correct.

So I'd propose to replace DAEMON with a direct reference to the program. What do you think?

DAEMON can be useful sometime in the future if we homogenize the scripts so well that we can use a template that is sourced after setting a small of variables (DAEMON, DAEMON_ARGS, PIDFILE, and so on). Perhaps we should use an EXECFILE variable instead of /usr/bin/$DAEMON.

Signature · 1 line
Carlos Santos (Casantos) - DATACOM, P&D
#8 lore raw

PATCH v5 1/1 package/ntp: sntp time sync script

Quoted 27 lines · Carlos Santos
Quoted 27 lines

From: "Arnout Vandecappelle" <[email protected]>
To: "Matthew Weber" <[email protected]>, "buildroot" <[email protected]>
Cc: "Oscar Gomez Fuente" <[email protected]>, "Carlos Santos" <[email protected]>
Sent: Domingo, 3 de fevereiro de 2019 18:00:33
Subject: Re: [Buildroot] [PATCH v5] package/ntp: sntp time sync script

Hi Matt,

I've finally applied to master since it really is a useful feature and it works. However, I have a few additional remarks. Also one for Carlos, the init script dude :-)

On 12/12/2018 04:45, Matt Weber wrote:
[snip]

package/ntp/S48sntp line 3

Quoted 3 lines
package/ntp/S48sntp new file +3 -0
+#!/bin/sh
+
+DAEMON="sntp"

Carlos, I'm starting to doubt the usefulness of this DAEMON variable. Other variables are prefixed by SNTP_, only this one isn't. In other init scripts you started using PROGRAM instead because it isn't actually a daemon.

However, the only reason to make it a variable is to make it easier to copy and adapt an existing init script. But really, doing a search/replace of that string is not so much work. And you anyway need to review the entire file, e.g. /usr/bin/$DAEMON is used which may not be correct.

Quoted 7 lines
Quoted 2 lines

So I'd propose to replace DAEMON with a direct reference to the program. What do you think?

DAEMON can be useful sometime in the future if we homogenize the scripts so well that we can use a template that is sourced after setting a small of variables (DAEMON, DAEMON_ARGS, PIDFILE, and so on). Perhaps we should use an EXECFILE variable instead of /usr/bin/$DAEMON.

That's a great counterexample why a template won't work :-) Sometimes it's
/usr/sbin or /bin or /sbin or maybe something else still. So I think making it a template that can be sourced is going to lead us too far - there are already a couple of init-script-management tools; if we really want that, we should use one of those. But we don't want that, we really do want individually maintained init scripts. However, it's easier to maintain / review them if they follow a common structure. And my point is: I don't think the DAEMON / PROGRAM / EXECFILE variable adds much value.

Regards,
Arnout