Date: Thu, 03 May 2007 21:20:36 +0200 From: des@des.no (Dag-Erling =?utf-8?Q?Sm=C3=B8rgrav?=) To: Chuck Swiger <cswiger@mac.com> Cc: "illoai@gmail.com" <illoai@gmail.com>, Duane Hill <d.hill@yournetplus.com>, freebsd-questions@freebsd.org Subject: Re: Time Synchronizing Between Two Servers Message-ID: <86y7k5ogsb.fsf@dwp.des.no> In-Reply-To: <4639FAB6.9050701@mac.com> (Chuck Swiger's message of "Thu, 03 May 2007 11:07:34 -0400") References: <20070503014137.I3544@duane.dbq.yournetplus.com> <a969fbd10705021849g64f4752fobd5b6a817254ba28@mail.gmail.com> <20070503015723.S3544@duane.dbq.yournetplus.com> <d7195cff0705022217k4f0aaf2fibd2bfeb97b6498c8@mail.gmail.com> <4639FAB6.9050701@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Swiger <cswiger@mac.com> writes: > Simply setting the date upon system boot and maybe once a day using > cron to call ntpdate or whatever is probably good enough for any > client machine, and OK for non-important servers where the exact > timekeeping doesn't matter much. Why, when setting up ntpd is so easy? On your router: # hostname router.example.com # cat >/etc/ntp.conf server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org ^D # cat >>/etc.rc.conf ntpdate_enable=3D"YES" ntpd_enable=3D"YES" ^D # /etc/rc.d/ntpdate start # /etc/rc.d/ntpd start On every other machine in your network: # cat >/etc/ntp.conf server router.example.com ^D # cat >>/etc.rc.conf ntpdate_enable=3D"YES" ntpd_enable=3D"YES" ^D # /etc/rc.d/ntpdate start # /etc/rc.d/ntpd start Everything else is already taken care of. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86y7k5ogsb.fsf>