From 33e058968c132b5d9fe55baf8df88399d0a3b97b Mon Sep 17 00:00:00 2001 From: Jason McIntyre Date: Fri, 8 Aug 2003 10:13:34 +0000 Subject: refer to RFCs consistently (RFC XXXX); --- usr.sbin/rdate/rdate.8 | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'usr.sbin/rdate') diff --git a/usr.sbin/rdate/rdate.8 b/usr.sbin/rdate/rdate.8 index 9a304622fa3..2af93654760 100644 --- a/usr.sbin/rdate/rdate.8 +++ b/usr.sbin/rdate/rdate.8 @@ -1,4 +1,4 @@ -.\" $OpenBSD: rdate.8,v 1.23 2003/06/12 12:59:52 jmc Exp $ +.\" $OpenBSD: rdate.8,v 1.24 2003/08/08 10:13:33 jmc Exp $ .\" $NetBSD: rdate.8,v 1.4 1996/04/08 20:55:17 jtc Exp $ .\" .\" Copyright (c) 1994 Christos Zoulas @@ -43,22 +43,22 @@ .Nm displays and sets the local date and time from the host name or address given as the argument. -The time source may be an RFC868 TCP protocol server, +The time source may be an RFC 868 TCP protocol server, which is usually implemented as a built-in service of .Xr inetd 8 , -or an RFC1361 protocol SNTP/NTP server. +or an RFC 1361 protocol SNTP/NTP server. By default, .Nm -uses the RFC868 TCP protocol. +uses the RFC 868 TCP protocol. .Pp The options are as follows: .Bl -tag -width Ds .It Fl n -Use SNTP (RFC1361) instead of the RFC868 time protocol. +Use SNTP (RFC 1361) instead of the RFC 868 time protocol. .It Fl c Correct leap seconds. Sometimes required when synchronizing to an NTP server. -When synchronizing using the RFC868 protocol, use this option only if the +When synchronizing using the RFC 868 protocol, use this option only if the server does not correctly account for leap seconds. You can determine if you need this parameter if you sync against an NTP server (with this parameter) or (recommended) check with a local radio -- cgit v1.2.3