-----BEGIN PGP SIGNED MESSAGE----- On 07-Jan-99 Leon McClatchey wrote: || || Hi:-) || || || > || > That is where the xntpd server comes into play. This daemon connects to || > reliable time sources on the net, and then assuming that you want it to do || > so, || > will update your machine. I am not familiar with SuSE 5.1, but in 5.3 you || > would find it in /sbin/init.d/xntpd. || > || > There are a few confiuration files that you need to set up which will || > point the || > daemon out to the right machines to sync with. You might want to do a man || > on || > ntp and ntpdate. One word of warning, if you are syncing via dial-up, you || > may || > want to make sure that xntpd does not fire-up at boot time. Makes for a || > long wait as you are waiting for it to search out machines that it cannot || > connect to. || > || || I have looked at the manual pages for ntp and ntpdate and for some reason || it makes me feel a little bit on the braindead side:-) A long time ago, I || had a dos program that could be used to dial up to a time server and then it || had to be configured to convert the time it got into a time for the pc. || From what I could tell from the man pages on ntpdate, that conversion is not || necessary as long as you connect to the || correct server? That is the part that I am finding a little bit of || difficulty, || finding a server that is local CST6CDT to my time zone? I've looked for || sample || configuration files, and could not find anything. If I could locate the || right || server than I could test to see if my time really needed to be updated, and || if it || did, do so. Also, when "logging into a timeserver" is it necessary to || provide a uid || and password? I've got diald set up so that demand dialing is available || throughout || most of the day, and from about 8:00pm to about 2:30am. I figure that I || can use || crontab to initiate a internet hookup durring that time? But, will diald || respond to || the nftdate check? (It does respond to the "dig" command for the monthly || update of || the root.cache for my nameserver). || || > || > I start up xntpd in my /etc/ppp/ip-up.local and stop it when I shutdown my || > PPP || > connection. || > || || Can Xntpd be set up to run a one shot deal say once a week to keep the time || current? Ok, a lot of questions in a a short paragraph! :?) The easiest way to handle this is to first give you a copy of my /etc/ntp.conf. Put this file in /etc and then start of xntpd how ever you want... You could start it in ip-up.local as I suggested before. There is no problem with cron, if you want to add in the other stuff to get your PPP connection going. I would recommend against diald, because once the xntpd daemon gets going it is a bit anal about making sure it is in sync. You would find that your diald up times would be quite excessive. On the other hand, you could possible cron ntpdate to do the same thing. There would be no problem with diald doing that occasionally. Hope this helps! - --- Kim C. Callis -- [EMAIL PROTECTED] ********************************* * When it absolutely, * * Positively has to be * * Destroyed over night! * * * * (800) MARINES * ********************************* -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQCVAwUBNpR42iaI5lr1ZTHJAQEJGwP+KbL3T8mIHJfYvCM/B9CG9w7mrutEiSMp fGpMfw0jm8vSMOG+dKlqS605gtUBqTxqCe1JvmmJFbtNGeiJmsKLtfadcYgW7RiE pNvp3XfNiNpCG1LWMHND9ZUe09tkVCyKe3lv4Jiu6DZjIpn82JUlsf4+fogO6t7X /q1jvZTpym8= =NF64 -----END PGP SIGNATURE-----
# # NTP configuration file (ntp.conf) # # Generic configuration file for UDel NTP stratum-2 time servers. Don't # forget each server should have a /etc/ntp.drift and /etc/ntp.keys file. # # Stratum-1 peers. Each server should chime two different stratum-1 # servers from the following list. Each stratum-1 server should be used # only once. # peer 128.8.10.1 # umd1.umd.edu #peer 18.72.0.3 version 2 # bitsy.mit.edu #peer 132.249.16.1 # fuzz.sdsc.edu #peer 128.118.46.3 version 2 # otc1.psu.edu peer 128.9.2.129 # wwvb.isi.edu #peer 130.43.2.2 version 2 # apple.com #peer 16.1.0.22 # clepsydra.dec.com #peer 130.105.1.156 version 2 # clock.osf.orga #peer 128.96.60.5 version 2 # pi.bellcore.com #peer 128.4.1.1 # rackety.udel.edu #peer 129.116.3.5 # shorty.chpc.utexas.edu # # Stratum-2 peers. Each server should chime all of the others in this # list except itself. # peer 128.175.1.1 # huey.udel.edu (VAX) peer 128.175.1.2 # dewey.udel.edu (VAX) peer 128.175.1.3 # louie.udel.edu (SPARC) peer 128.175.2.15 # snow-white.ee.udel.edu (SPARC) peer 128.175.7.4 # sol.cis.udel.edu (SPARC) # # Miscellaneous stuff # driftfile /etc/ntp.drift # path for drift file # # Authentication stuff. Note the different authentication delay on # VAX and SPARC. # #keys /usr/local/etc/ntp.keys # path for key file #trustedkey 1 2 15 # define trusted keys #requestkey 15 # key (7) for accessing server variables #controlkey 15 # key (6) for accessing server variables
