Unfortunately windows update restarted the machine last night so I have
to wait for things to stabilise again before posting stats :\
Mark
Have you not set Windows Update to inform but not automatically install?
Cheers,
David
___
questions mailin
On Fri, Dec 9, 2011 at 05:33, Mark C. Stephens wrote:
> Hi Got this error today when I restarted ntpd, probably not anything, but
> just checking:
>
>
> refclock_params: time_pps_kcbind: Unknown error: 45
>
>
> Win2003 x86
> ntpd 4.2.7p224-o Oct 14 19:58:02.91 (UTC-00:00) 2011
> using serialpps
>
Hi Got this error today when I restarted ntpd, probably not anything, but just
checking:
refclock_params: time_pps_kcbind: Unknown error: 45
Win2003 x86
ntpd 4.2.7p224-o Oct 14 19:58:02.91 (UTC-00:00) 2011
using serialpps
relevant conf:
server 127.127.20.1 minpoll 4 maxpoll 4 mode 24 prefer
f
Hi Danny,
Have you got a chance to go through the code for this?
Here though the socket bind is failing the multicast registration is
happening successfully (which are shown by the debug traces here.)
Does that have anything to infer here?
>
> On Thu, Dec 8, 2011 at 9:58 AM, Danny Mayer wrote:
On 2011-12-08T07:38:51+, Paul Duncan wrote:
> Okay, so I have changed the ntp.conf so that it now looks like this:
>
> server 127.127.20.0 prefer mode 2 minpoll 4 maxpoll 4
> server 127.127.22.0
>
> tos mindist 0.250
>
> statistics loopstats
> statsdir /var/log/ntp/
> filegen loopstats file
The computer is a HP (Compaq) DL360 G1 running 32bit Windows server 2003.
Unfortunately windows update restarted the machine last night so I have to wait
for things to stabilise again before posting stats :\
Mark
-Original Message-
From: Miroslav Lichvar [mailto:mlich...@redhat.com]
On Thu, 08 Dec 2011 20:14:28 +, Harlan Stenn wrote:
> Bruce wrote:
>> On Wed, 07 Dec 2011 23:56:08 +, Harlan Stenn wrote:
>
>> Short
>> of that, getting close to the right offset before starting ntpd means:
>> 1) processes that depend on reasonably-close time synchronization
>>(rsync,
Bruce wrote:
> On Wed, 07 Dec 2011 23:56:08 +, Harlan Stenn wrote:
>
> > Bruce wrote:
> >> I do run sntp to set the clock before starting ntpd (so I don't need
> >> ntpdate). Setting the clock this way at least gets the time offset in
> >> the ballpark before ntpd starts.
> >
> > OK, and exa
On 2011-12-08, Joe Smithian wrote:
> A,N,S, and M keys are defined in the man ntp.keys
>
> http://www.gsp.com/cgi-bin/man.cgi?section=5&topic=ntp.keys
I have the current ntp-dev installed and:
$ man ntp.keys
No manual entry for ntp.keys
--
Steve Kostecke
NTP Public Services Project - http://
On Thu, Dec 8, 2011 at 14:38, Joe Smithian wrote:
> A,N,S, and M keys are defined in the man ntp.keys
>
> http://www.gsp.com/cgi-bin/man.cgi?section=5&topic=ntp.keys
That's a good example of why one should be suspicious of man pages for
ntpd and friends -- the distribution docs are maintained as
They are milliseconds. If ntpd on Windows can really keep the clock
stable to to ~10 microseconds, the recent suggestion posted here to
never use Windows for serious timekeeping might need to be revisited.
--
Miroslav Lichvar
Here's what I see on my Windows PCs:
http://www.satsignal.eu/mrtg/p
A,N,S, and M keys are defined in the man ntp.keys
http://www.gsp.com/cgi-bin/man.cgi?section=5&topic=ntp.keys
On Mon, Dec 5, 2011 at 11:48 AM, Dave Hart <
davehart_gmail_exchange_...@davehart.net> wrote:
> On Mon, Dec 5, 2011 at 14:34, Joe Smithian wrote:
> > Hi Dave,
> >
> > Thanks Dave for y
On Mon, Dec 05, 2011 at 01:16:32PM +, Duncan, Paul A. wrote:
> So, to summarise my questions:
>
> 1) Is ntpd getting the PPS information?
Likely not.
I'm fairly sure that your problem is that you don't have the timepps.h
header installed (this is the header that defines the PPSAPI functions
On 12/8/2011 7:37 AM, Bruce Lilly wrote:
> Some code in ntpd applies a dither using ntp_random. However,
> ntp_random (which is also used elsewhere, e.g. in getting an
> initial association ID) generates only positive integers,
> resulting in a one-sided offset bias. The following patch
> compens
On Thu, Dec 8, 2011 at 11:50, Miroslav Lichvar wrote:
> They are milliseconds. If ntpd on Windows can really keep the clock
> stable to to ~10 microseconds, the recent suggestion posted here to
> never use Windows for serious timekeeping might need to be revisited.
It can, with the stars aligned
Some code in ntpd applies a dither using ntp_random. However,
ntp_random (which is also used elsewhere, e.g. in getting an
initial association ID) generates only positive integers,
resulting in a one-sided offset bias. The following patch
compensates for this bias by offsetting the return value
f
On Wed, 07 Dec 2011 23:56:08 +, Harlan Stenn wrote:
> Bruce wrote:
>> I do run sntp to set the clock before starting ntpd (so I don't need
>> ntpdate). Setting the clock this way at least gets the time offset in
>> the ballpark before ntpd starts.
>
> OK, and exactly why do you need "the tim
On Thu, Dec 08, 2011 at 07:53:15AM +, Mark C. Stephens wrote:
> Hello Sir Unrah,
>
>
> I just use ntpq -p. I am using Dave Harts rather excellent port to windows:
>
> C:\Program Files\NTP\bin>ntpq -p
> remote refid st t when
> pollr
On Thu, Dec 08, 2011 at 03:55:50AM +, Mark C. Stephens wrote:
> Oh no I am quite happy with my hp3325A ;)
>
>
> Well Okay, after a slight detour trying to get ilo100 to work, I loaded
> centos 6.0 x64 on the DL165 G2 (computer) and found it has 3.3V PCI slots. So
> none of my Serial I/O car
19 matches
Mail list logo
