On Thu, Mar 24, 2011 at 1:45 AM, prashant sherin wrote:
> Hi All,
> Thanks for the discussion and suggestions.
> I accept there are disadvantages in syncing the local clock using ntpd
> -q.
> My only question was whether the drift file will be created/used/
> updated by ntpd when it is used with -
Hi All,
Thanks for the discussion and suggestions.
I accept there are disadvantages in syncing the local clock using ntpd
-q.
My only question was whether the drift file will be created/used/
updated by ntpd when it is used with -q option.
Thanks and Regards,
Prashant
Chris Albertson wrote:
I'd bet any musician could do better than 0.1 sec. If you are playing
piano and the timing of a note is off by as much as .1 sec it sounds
like an error.MIDI is used to record musical performances and it
uses a "tick" about every 10ms or 100 or 128 per second. That is
On Tue, Mar 22, 2011 at 11:12 PM, unruh wrote:
> On 2011-03-23, Hal Murray wrote:
>
> You can probably do better than that. That is for the reaction to
> something that you do not expect. Ie, you have decide that the event has
> occured and then send the messages to your finger to press. However
On 2011-03-22, bombjack wrote:
> I am fully aware fo how ntpd should be used, i.e. 24/7/365, but that
> is not what I am asking for. As I stated above, I need to make sure
> the system clock is roughly (your wrist watch would do) the correct
> time ASAP during boot as other systems will use this
On 23.3.2011 8:07, Hal Murray wrote:
You can probably do better than that. That is for the reaction to
something that you do not expect. Ie, you have decide that the event has
occured and then send the messages to your finger to press. However for
the timing, you know exactly when it is going t
>You can probably do better than that. That is for the reaction to
>something that you do not expect. Ie, you have decide that the event has
>occured and then send the messages to your finger to press. However for
>the timing, you know exactly when it is going to occur. You can get
>yourself into
On 2011-03-23, Hal Murray wrote:
>
>>> oh, come off it. Your reaction time is nowhere near what ntp -q would
>>> give you. Using ntp -q run once every hour, and assuming say a 20PPM
>>> drift for the crystal, his clock would be out by less than a 100 ms due to
>>> the
>>> drifting, and your react
>> oh, come off it. Your reaction time is nowhere near what ntp -q would
>> give you. Using ntp -q run once every hour, and assuming say a 20PPM
>> drift for the crystal, his clock would be out by less than a 100 ms due to
>> the
>> drifting, and your reaction time with your watch ( and wyour wat
On 3/22/2011 1:22 PM, unruh wrote:
On 2011-03-22, David J Taylor wrote:
He can do that if he wants to. That was why the -q option was designed
into ntpd-- one time setting of the clock time. However it cannot create
a drift file. If he wants a drift file then as you say, he must run it
continuo
oh, come off it. Your reaction time is nowhere near what ntp -q would
give you. Using ntp -q run once every hour, and assuming say a 20PPM
drift for the crystal, his clock would be out by less than a 100 ms due to the
drifting, and your reaction time with your watch ( and wyour watch) are
nowhe
"unruh" wrote in message
news:slrniohsae.ksv.un...@wormhole.physics.ubc.ca...
[]
I have seen the drift out by 400PPM at around the hour mark. ntpd
massively overswings to correct any intial error in the clock ( say a
few ms) , and then gradually
settles back toward the correct drift rate. Th
On 3/22/2011 12:07 PM, bombjack wrote:
On Mar 22, 4:20 pm, "Richard B. Gilbert"
wrote:
On 3/22/2011 2:56 AM, prashant sherin wrote:
ntpd is intended to for continuous, not periodic running. You are not
using it correctly.
Cheers,
David
Thanks for the quick reply.
ntpd does allow
On 2011-03-22, Chris Albertson wrote:
> On Mon, Mar 21, 2011 at 11:38 PM, prashant sherin wrote:
>> Hi,
>> I would like to know if ntpd would use the driftfile specified in /etc/
>> ntp.conf file if it is run periodically using crontab with -q option
>> as below:
>
> That is a rather resource int
On 2011-03-22, David J Taylor wrote:
>
> "unruh" wrote in message
> news:slrniohmmc.6v5.un...@wormhole.physics.ubc.ca...
> []
>> ntpd -q is a replacemtn for ntpdate, which was typically run from cron,
>> and he is doing, and it is an "acceptable" procedure if for example you
>> do not want a dae
"unruh" wrote in message
news:slrniohmmc.6v5.un...@wormhole.physics.ubc.ca...
[]
ntpd -q is a replacemtn for ntpdate, which was typically run from cron,
and he is doing, and it is an "acceptable" procedure if for example you
do not want a daemon running which could have (unknown to you) secur
On 2011-03-22, Richard B. Gilbert wrote:
> On 3/22/2011 2:56 AM, prashant sherin wrote:
>>> ntpd is intended to for continuous, not periodic running. You are not
>>> using it correctly.
>>>
>>> Cheers,
>>> David
>>
>> Thanks for the quick reply.
>> ntpd does allow us to run this way. From the ntp
On 2011-03-22, bombjack wrote:
> On Mar 22, 4:20?pm, "Richard B. Gilbert"
> wrote:
>> On 3/22/2011 2:56 AM, prashant sherin wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> >> ntpd is intended to for continuous, not periodic running. ?You are not
>> >> using it correctly.
>>
>> >> Cheers,
>> >> David
>>
>> >
On 2011-03-22, David J Taylor wrote:
>> He can do that if he wants to. That was why the -q option was designed
>> into ntpd-- one time setting of the clock time. However it cannot create
>> a drift file. If he wants a drift file then as you say, he must run it
>> continuously.
>
> You could look a
On Mon, Mar 21, 2011 at 11:38 PM, prashant sherin wrote:
> Hi,
> I would like to know if ntpd would use the driftfile specified in /etc/
> ntp.conf file if it is run periodically using crontab with -q option
> as below:
That is a rather resource intensive way to run NTP. You use fewer
CPU cycle
On Mar 22, 4:20 pm, "Richard B. Gilbert"
wrote:
> On 3/22/2011 2:56 AM, prashant sherin wrote:
>
>
>
>
>
>
>
>
>
> >> ntpd is intended to for continuous, not periodic running. You are not
> >> using it correctly.
>
> >> Cheers,
> >> David
>
> > Thanks for the quick reply.
> > ntpd does allow us t
On 3/22/2011 2:56 AM, prashant sherin wrote:
ntpd is intended to for continuous, not periodic running. You are not
using it correctly.
Cheers,
David
Thanks for the quick reply.
ntpd does allow us to run this way. From the ntpd man page:
-q Exit the ntpd just after the first time the c
Thanks all for the suggestions and explanation.
Regards,
Prashant
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
He can do that if he wants to. That was why the -q option was designed
into ntpd-- one time setting of the clock time. However it cannot create
a drift file. If he wants a drift file then as you say, he must run it
continuously.
You could look at it that way, Bill, if all he needs is a one-off s
prashant sherin wrote:
The idea is to use it as ntp client.
It would only be an SNTP client, used like this.
My understanding is that if I run ntpd in daemon mode, it will
also act like an NTP server listening on UDP port 123. I think running
ntpd with -q option
would prevent the server from
On 2011-03-22, prashant sherin wrote:
>> ntpd is intended to for continuous, not periodic running. ?You are not
>> using it correctly.
>>
>> Cheers,
>> David
>
> Thanks for the quick reply.
> ntpd does allow us to run this way. From the ntpd man page:
>
> -q Exit the ntpd just after the firs
On 2011-03-22, David J Taylor wrote:
>> Hi,
>> I would like to know if ntpd would use the driftfile specified in /etc/
>> ntp.conf file if it is run periodically using crontab with -q option
>> as below:
>>
>> /usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -g -q -L eth0
>>
>> I do not find any dri
On 2011-03-22, prashant sherin wrote:
> Hi,
> I would like to know if ntpd would use the driftfile specified in /etc/
> ntp.conf file if it is run periodically using crontab with -q option
> as below:
>
> /usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -g -q -L eth0
>
> I do not find any drift file
On Mar 22, 12:18 pm, unruh wrote:
> On 2011-03-22, prashant sherin wrote:
>
>
>
> >> ntpd is intended to for continuous, not periodic running. ?You are not
> >> using it correctly.
>
> >> Cheers,
> >> David
>
> > Thanks for the quick reply.
> > ntpd does allow us to run this way. From the ntpd ma
Hi,
I would like to know if ntpd would use the driftfile specified in /etc/
ntp.conf file if it is run periodically using crontab with -q option
as below:
/usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -g -q -L eth0
I do not find any drift file being created at the specified location.
Thanks and
Hi,
I would like to know if ntpd would use the driftfile specified in /etc/
ntp.conf file if it is run periodically using crontab with -q option
as below:
/usr/sbin/ntpd -u ntp:ntp -p /var/run/ntpd.pid -g -q -L eth0
I do not find any drift file being created at the specified location.
Thanks an
> ntpd is intended to for continuous, not periodic running. You are not
> using it correctly.
>
> Cheers,
> David
Thanks for the quick reply.
ntpd does allow us to run this way. From the ntpd man page:
-q Exit the ntpd just after the first time the clock is set.
This behavior mimics that o
32 matches
Mail list logo
