Date: Sat, 25 Dec 2004 00:53:52 GMT From: "Jay O'Brien" <jayobrien@att.net> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/75479: sysinstall time servers list has out of date entries Message-ID: <200412250053.iBP0rqZS055638@www.freebsd.org> Resent-Message-ID: <200412250100.iBP10kR2016386@freefall.freebsd.org>
index | next in thread | raw e-mail
>Number: 75479
>Category: misc
>Synopsis: sysinstall time servers list has out of date entries
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Sat Dec 25 01:00:46 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Jay O'Brien
>Release: 5.3 RELEASE
>Organization:
>Environment:
FreeBSD server1.jayobrien.net 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #0: Sun Dec 12 22:59:32 PST 2004 root@server1.jayobrien.net:/usr/obj/usr/src/sys/GENERIC i386
>Description:
I noted my computer's time was off a couple of minutes. I
found that nntp wasn't working. I had selected the second
Washington state server, when using the sysinstall process
to set up time syncronization.
I learned that neither of the time servers shown for WA,
clock.tricity.wsu.edu or ntp.tcp-udp.net would resolve in
DNS. As my DSL line hits the internet in Seattle, I wanted
a Washington time server; I edited ntpdate_flags in rc.conf
to now read time.windows.com (also in WA), and now my
computer time is correct. I promise to not tell Microsoft!
>How-To-Repeat:
Check the time server list against the targets.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412250053.iBP0rqZS055638>