On 2012-07-09, Ron Frazier (NTP) wrote:
>
>
>
>
> unruh wrote:
>
>>On 2012-07-09, Dave Hart wrote:
>>> On Mon, Jul 9, 2012 at 18:14 UTC, Fritz Wuehler wrote:
I noticed the clock on my main desktop was off by 28 minutes today
>>and it
increased to 45 minutes. I resync'd with ntpdate man
On 2012-07-09, Dave Hart wrote:
> On Mon, Jul 9, 2012 at 21:00 UTC, unruh wrote:
>> If he is having trouble keeping many second sync with pool servers, he
>> is going to have trouble with keeping sync with a master. And if that
>> master goes out for some reason, he will be totally up the creek.
>
unruh wrote:
>On 2012-07-09, Dave Hart wrote:
>> On Mon, Jul 9, 2012 at 18:14 UTC, Fritz Wuehler wrote:
>>> I noticed the clock on my main desktop was off by 28 minutes today
>and it
>>> increased to 45 minutes. I resync'd with ntpdate manually and it has
>drifted
>>> behind again about 7 mi
On Mon, Jul 9, 2012 at 21:00 UTC, unruh wrote:
> If he is having trouble keeping many second sync with pool servers, he
> is going to have trouble with keeping sync with a master. And if that
> master goes out for some reason, he will be totally up the creek.
There's a big difference between synch
On 2012-07-09, Dave Hart wrote:
> On Mon, Jul 9, 2012 at 18:14 UTC, Fritz Wuehler wrote:
>> I noticed the clock on my main desktop was off by 28 minutes today and it
>> increased to 45 minutes. I resync'd with ntpdate manually and it has drifted
>> behind again about 7 minutes in the last few hour
On 2012-07-09, Kennedy, Paul wrote:
> Nazim,
> If all you need is relative timing, pick a computer as master (a modern
> one one you rarely reboot is a good choice), edit the ntp.conf file to
> use a series (say 3) of external pool servers. then goto the other 3
> machines, edit the ntp.conf file
On 7/9/2012 2:14 PM, Fritz Wuehler wrote:
I noticed the clock on my main desktop was off by 28 minutes today and it
increased to 45 minutes. I resync'd with ntpdate manually and it has drifted
behind again about 7 minutes in the last few hours.
You do not mention the direction of the error whic
On 7/9/2012 2:14 PM, Fritz Wuehler wrote:
I noticed the clock on my main desktop was off by 28 minutes today and it
increased to 45 minutes. I resync'd with ntpdate manually and it has drifted
behind again about 7 minutes in the last few hours.
NTP will only correct for local clock error up to
On Mon, Jul 9, 2012 at 18:14 UTC, Fritz Wuehler wrote:
> I noticed the clock on my main desktop was off by 28 minutes today and it
> increased to 45 minutes. I resync'd with ntpdate manually and it has drifted
> behind again about 7 minutes in the last few hours.
>
> I am using ntp version 4.2.4p7
I noticed the clock on my main desktop was off by 28 minutes today and it
increased to 45 minutes. I resync'd with ntpdate manually and it has drifted
behind again about 7 minutes in the last few hours.
I am using ntp version 4.2.4p7 which was installed with Slackware on Linux
kernel 2.6.29.6. Unt
"Nazmul Islam" wrote in message
news:caftrfezn5mhq_bodeg5kz7l2kga5s6ngsmfbhyksmxxm9gf...@mail.gmail.com...
Hello,
I have not used ntp processing before. I apologize in advance if my
questions seem too novice.
I am trying to synchronize the clocks of four computers. The timing does
not have
11 matches
Mail list logo
