He's right just about any system will do. But if you're doing making builds across the network and timing needs to be pretty exact so they dont fail. I'd use an actual time server that uses an atomic clock like the one i listed previously On Fri, 8 Dec 2000, Doug McLaren wrote: > On Fri, Dec 08, 2000 at 01:21:02PM -0600, Bill Dodd wrote: > > | I see you found an rdate, but if you have ntp installed you could > | also use ntpdate to do the same thing. > | > | I've got the same old bios 1994 problem; you may want to play with your rc > | files to get it to do the rdate/ntp stuff before cron starts. That keeps > | cron from seeing the big time step and deciding to run a bunch of > | daily/weekly stuff that it doesn't need to. > > Yes, ntpdate is what you want -- it uses the same protocol as ntp, so > you don't need to find a special server for it. > > As for rdate, most any Unix box that doesn't have the `small services' disabled in >inetd will do. For example ... > > % rdate piglet.cc.utexas.edu > [piglet.cc.utexas.edu] Fri Dec 8 14:22:32 2000 > > % rdate cs.utexas.edu > [cs.utexas.edu] Fri Dec 8 14:23:04 2000 > > % rdate www.utexas.edu > [www.utexas.edu] Fri Dec 8 14:23:32 2000 > > % rdate eff.org > [eff.org] Fri Dec 8 14:31:44 2000 > > But ntpdate is better. > > -- > Doug McLaren, [EMAIL PROTECTED] > I find this corpse guilty of carrying a concealed weapon and I fine it $40. > -- Judge Roy Bean, finding a pistol and $40 on a man he'd > just shot. > --------------------------------------------------------------------------- > Send administrative requests to [EMAIL PROTECTED] > --------------------------------------------------------------------------- Send administrative requests to [EMAIL PROTECTED]
