On Wed, 19 Sep 2007 12:24:57 +1200 Roger Searle <[EMAIL PROTECTED]> wrote:
> Steve Holdoway wrote: > > On Wed, 19 Sep 2007 11:27:47 +1200 > > Roger Searle <[EMAIL PROTECTED]> wrote: > > > > > >> I'm pleased to report that time on that box is no longer drifting. So I > >> won't need to implement one of these options, and will give some thought > >> to the "no" answer to point 1. > >> > >> Thanks to everyone for their replies. > >> Roger > >> > >> > > The ntp daemon should be running all the time. There is no need or reason > > to ever stop and start it, as it's always working. > > > > Steve > > > Sure, but the original situation was that the daemon was NOT able to > keep time in sync, and that the ntp restart DID fix it temporarily. If that is the case then I expect that you'll find that there's a call to ntpdate in the start section of /etc/init.d/ntp, as this functionality is *not* a part of the ntp daemon. > > Following from the various updates and configuration changes made > yesterday, ntp is now able to do it's job. I'm happy . . . Whopee! I ended up with custom kernels, weird boot parameters and allsorts to get mine working. In the end, I think it was a kernel update that fixed it. Just a poor choice of motherboard I on my part I think. I still can't run more than 3GB memory without crashing, and there are no bios updates available ): > Roger
pgpDDy8pU7o8R.pgp
Description: PGP signature
