Path: utzoo!utstat!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!yarra!melba.bby.oz.au!leo!gnb From: gnb@bby.oz (Gregory N. Bond) Newsgroups: news.software.nntp Subject: Re: Suggested NNTP enhancements for user access control Message-ID: Date: 13 Nov 89 02:20:27 GMT References: <10095@ucsd.Edu> <1802@gazette.bcm.tmc.edu> <1544@intercon.com> <1546@intercon.com> Sender: news@melba.bby.oz.au Organization: Burdett, Buckeridge and Young Ltd. Lines: 27 In-Reply-To: amanda@intercon.com's message of 11 Nov 89 20:12:00 GMT In article <1546@intercon.com> amanda@intercon.com (Amanda Walker) writes: NTP is probably the way to go. I wonder if a lonely standalone network (like ours :-)) could run NTP and sync up by modem with an NBS (or is it NIST these days?) modem-equipped cesium clock every so often? That could be nifty... (especially when said clock is only a local call :-)). (This is off the topic of nntp, but...) We run ntp here on an isolated network. It runs quite happily. I did some tests to find the machine with the most stable clock. (By sheer chance it was the workstation on my desk). This is set up to use the local clock as a stratum-3 server. All the file severs peer with my workstation and one other server. One server with an almost-as-stable clock has a stratum-4 local clock server. All workstations are peered to their server. Thus all machines are synced to my workstation, and if that's down they resync to the other server, otherwise they run free. Works like a charm. I'd be happy to share experiences and ntp.conf files if anyone is interested. Greg. -- Gregory Bond, Burdett Buckeridge & Young Ltd, Melbourne, Australia Internet: gnb@melba.bby.oz.au non-MX: gnb%melba.bby.oz@uunet.uu.net Uucp: {uunet,pyramid,ubc-cs,ukc,mcvax,prlb2,nttlab...}!munnari!melba.bby.oz!gnb