opnsense-src/etc/rc.d/ntpdate

#!/bin/sh
#
# $FreeBSD$
#

# PROVIDE: ntpdate
# REQUIRE: NETWORKING syslogd
# KEYWORD: nojail

. /etc/rc.subr

name="ntpdate"
desc="Set the date and time via NTP"
rcvar="ntpdate_enable"
stop_cmd=":"
start_cmd="ntpdate_start"

ntpdate_start()
{
	if [ -z "$ntpdate_hosts" -a -f "$ntpdate_config" ]; then
		ntpdate_hosts=`awk '
			/^server[ \t]*127.127/      {next}
			/^(server|peer|pool)/       {
			    if ($2 ~/^-/)           {print $3}
			    else                    {print $2}}
		' < "$ntpdate_config"`
	fi
	if [ -n "$ntpdate_hosts" -o -n "$rc_flags" ]; then
		echo "Setting date via ntp."
		${ntpdate_program:-ntpdate} $rc_flags $ntpdate_hosts
	fi
}

load_rc_config $name
run_rc_command "$1"
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00			`#!/bin/sh`
			`#`
			`# $FreeBSD$`
			`#`

			`# PROVIDE: ntpdate`
Remove remnants of BIND from /etc, since there is no BIND in base now. Sorry, that would break users running head and BIND from ports, since ports rely on these scripts. The ports will be fixed soon. Reviewed by: erwin 2013-11-05 04:30:06 -05:00			`# REQUIRE: NETWORKING syslogd`
Remove the requirement for the FreeBSD keyword as it no longer makes any sense. Discussed with: dougb, brooks MFC after: 3 days 2004-10-07 09:55:26 -04:00			`# KEYWORD: nojail`
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00
			`. /etc/rc.subr`

			`name="ntpdate"`
- Add descriptions to most of the rc scripts. Those are mostly taken from their daemon's manpage and probably improved. - Consistently use "filesystem" not "file system". Approved by: bapt, brueffer Differential Revision: D452 2016-04-23 12:10:54 -04:00			`desc="Set the date and time via NTP"`
Prepare for the removal of set_rcvar() by changing the rcvar= assignments to the literal values it would have returned. The concept of set_rcvar() was nice in theory, but the forks it creates are a drag on the startup process, which is especially noticeable on slower systems, such as embedded ones. During the discussion on freebsd-rc@ a preference was expressed for using ${name}_enable instead of the literal values. However the code portability concept doesn't really apply since there are so many other places where the literal name has to be searched for and replaced. Also, using the literal value is also a tiny bit faster than dereferencing the variables, and every little bit helps. 2012-01-13 21:18:41 -05:00			`rcvar="ntpdate_enable"`
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00			`stop_cmd=":"`
			`start_cmd="ntpdate_start"`

			`ntpdate_start()`
			`{`
Allow $ntpdate_config to be NULL. Due to a lack of surrounding quotes, when ntpdate_config was set to NULL the conditional would (counter to prevailing logic) succeed -- leading to awk attempting to redirect from a NULL pathname standard-in. While we're here, make the script consistant with itself by removing the {curlies} around ntpdate_config (they are unnecessary). 2013-06-17 22:37:15 -04:00			`if [ -z "$ntpdate_hosts" -a -f "$ntpdate_config" ]; then`
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00			ntpdate_hosts=`awk '
			`/^server[ \t]*127.127/ {next}`
Follow r311103: add "pool" to the keywords that rc.d/ntpdate examines to find a server address in ntp.conf. Submitted by: Ronald Klop <ronald@klop.ws> Pointy hat to: ian 2017-01-10 19:14:47 -05:00			`/^(server\|peer\|pool)/ {`
Allow use of -6 option to "server" and "peer" in ntp.conf. MFC after: 1 week 2010-01-30 11:34:52 -05:00			`if ($2 ~/^-/) {print $3}`
			`else {print $2}}`
Allow $ntpdate_config to be NULL. Due to a lack of surrounding quotes, when ntpdate_config was set to NULL the conditional would (counter to prevailing logic) succeed -- leading to awk attempting to redirect from a NULL pathname standard-in. While we're here, make the script consistant with itself by removing the {curlies} around ntpdate_config (they are unnecessary). 2013-06-17 22:37:15 -04:00			' < "$ntpdate_config"`
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00			`fi`
			`if [ -n "$ntpdate_hosts" -o -n "$rc_flags" ]; then`
			`echo "Setting date via ntp."`
s/ntpdate_command/ntpdate_program/ to match rc.conf(5) and /etc/defaults/rc.conf. PR: conf/76188 Submitted by: Arne Wörner <arne_woerner at yahoo dot com> Approved by: murray MFC After: 7 days 2005-01-17 13:28:09 -05:00			`${ntpdate_program:-ntpdate} $rc_flags $ntpdate_hosts`
Bring back etc/rc.d/ntpdate as requested by scads of people. This isn't a complete backout as the ntpd_sync_on_start etc/rc.conf tunable is still present, though the default is now NO (was YES). Since we're no longer syncing time at startup by default when ntpd is enabled (as was the case 24hrs ago), remove UPDATING entry pointing out that ntpd(1) -g is slower than ntpdate(1). Hopefully ntpd_sync_on_start="YES" can be made the default for -CURRENT after 5.3 is cut. At the very least, this should be set to YES when a user requests to have ntpd enabled via sysinstall(1). Requested by: many 2004-09-14 21:08:33 -04:00			`fi`
			`}`

			`load_rc_config $name`
			`run_rc_command "$1"`