On Wed, Feb 8, 2012 at 19:55, Ron Frazier (NTP)
wrote:
> It doesn't appear to me that -M is related to process priority, but to
> internal scheduler timing. I tinkered around with the -P parameter a
> little, but couldn't detect any changes.
-P is a no-op for the Windows port. Windows doesn't u
Hello. I'm not sure who to address my reply to. Thanks for the link to
the configuration info. Here are a couple of quotes from it:
-M
Raise scheduler precision to its maximum (1 ms) using
timeBeginPeriod. (Windows only)
-P /priority/
To the extent permitted by the operating system,
On 2/3/2012 12:14 PM, E-Mail Sent to this address will be added to the
BlackLists wrote:
Ron Frazier (NTP) wrote:
So, the question is, how do I force this process to always start at the
priority that I want, rather than having to change it each time in Task
Manager?
Change the service
Ron Frazier (NTP) wrote:
> I decided to install the Meinburg NTP server and monitor
> on my Windows machines.
...
> I updated the key NTP programs and am using NTP version
> ntp-4.2.7p249-win-x86-bin from Dave Hart's website
...
> using RealTime priority creates periodic spikes where the
> o
On Thu, Feb 2, 2012 at 05:36, Ron Frazier (NTP)
wrote:
> The NTPD service always starts out at RealTime priority. I believe, based
> on some loopstats files, that using RealTime priority creates periodic
> spikes where the offset upwards of 35 ms or so. Also, the graph appears to
> have random j
Hello all,
My name is Ron Frazier and I'm a newbie to the list. I have several
computers that dual boot between Windows and Ubuntu. I've been using
NTP on Linux for a few years with its essentially default configuration
and a few NIST servers. I recently got interested in more accurate time
