> Rob Inglis said,
>
> > No, you're not 'duplicating' effort here. Really the only thing you should
> > do is set the address for your Time Server to the same address as your
>Nei replied
>
> Clock accuracy is more important than network closeness. It's no use
> using a nearby machine if it has an inaccurate clock. Machines
> dedicated as time servers should be correctly synchronised.
Perhaps I am missing something here, but, are a lot of people having
trouble with there machines keeping the correct time, O.K. I set my
clock manually twice a year to allow for summer time, but the rest of
the year I don't touch it unless something happens that throws the
time out completely, and I can't remember the last time that happened.
By changing it manually I would'nt do it while on line, so it could'nt
mess up any cost logger. So why are people so concerned with such
accuracy when it is obviously causing far more problems than it is
ever likely to cure.
Bryan
--
[EMAIL PROTECTED]
