steve at softgreen.co.uk
Wed Oct 24 09:17:14 BST 2001
I tracked down the problem eventually ... HUGELY embarrassing ... a 'colleague' had blocked NTP using
the filter on our router. Nothing quite like internal communication, is there?
Anyway, now working fine again. I will however follow up your suggestion of running ntpd on all the
Once again, thanks for your help.
Aled Morris wrote:
> On Tue, 23 Oct 2001, Steve Greenshaw wrote:
> >I run a variety of FreeBSD boxes, from 3.4 to 4.4. I have one of these using ntpd to sync with an
> >NTP stratum 1 server and then use 'ntpdate myntp.mydomain.com' as a regular cron job to keep the
> >other boxes near enough in time (absolute accuracy is not needed).
> Why not just run ntpd on these other boxes, seems like a lot less effort.
> You could broadcast NTP updates and use "broadcastclient", or just
> "server myntp".
> They could peer with each other to keep in sync if they lose the master
> > Recently however I see this
> >no server suitable for synchronization found
> It means the server myntp.mydomain.com isn't synced.
> Run "ntpdc -c peer" to view the status (post the output if you like)
> ++ Amazingly cheap server hosting in Telehouse, London ++
> ++ http://www.qix.co.uk/colo/ ++
> ------ FreeBSD UK Users' Group - Mailing List ------
More information about the Ukfreebsd