he value is in the range ntpd can handle (+/- 500 ppm)
everything is fine.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
FO buffer can hold
up to more than 600 capture events, which can then be retrieved either via
the PCI bus, or via the card's serial port.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp
erry MARTIN
Thierry has also sent this by private mail, and I've adviced him
to run "ntpd -gq" instead.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
card is fully synchronized because
the time from the GPS card's RTC is good enough as a startup for ntpd.
However, ntpd will wait anyway until the card is synchronized, before it
accepts the card as time source.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
_
used to implement
the system clock.
In this case the NTP daemon has no chance to discipline the clock properly.
May be you should use a newer distribution or at least kernel. The OpenSUSE
Live DVD might be helpful for a quick test.
Regards,
Martin
--
Hi Ulrich,
Ulrich Windl wrote:
> Martin Burnicki <[EMAIL PROTECTED]> writes:
>
> [...]
>> This does not seem to be a NTP problem (you are running ntp-4.2.0a though
>> SuSE calls the packet xntp-...).
>
> Just FYI: After a few years of complaint, the package
hey
both sync to GPS, but one of them also polls the other one, so you can see
how good or bad the accuracy across the WAN link actually is.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
s the
NTP program provided a much better accuracy than w32time.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
L PROTECTED] root]# ntpq -c ntpversion -version 192.168.0.1
> NTP version being claimed is 2
AFAIK the above is just the version of the protocol ntpq uses when sending
queries to the server, see the documentation for ntpq.
> ntpq [EMAIL PROTECTED] Tue Feb 24 06:32:31 EST 2004 (1)
Overall I'd say you should find out why your server does not claim to be
synchronized.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
e only seem to configure the PDC as their
upstream time server automatically if w32time is running on the PDC. I
don't know the way this is determined by the client.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ronize to the Linux box. Domain members
should then automatically sync to the PDC.
Other machines (e.g. Linux clients) on which you have to configure the
upstream time server manually should be configured to synchronize to the
Linux box directly.
Martin
--
Martin Burnicki
Meinber
he
manufacturer of the BIOS), or by some low level driver which may be
involved in setting the RTC.
You may try to keep an eye on when the RTC's second really changes. If it is
really off by 0.5 seconds after you have set it correctly this should be
clearly visible.
Martin
--
Martin Burnicki
se a
dedicated server like one of the PTB servers in order to yield more
comparable results.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
Marc Muehlfeld wrote:
> Martin Burnicki schrieb:
>> This seems to indicate that the new kernel implements the system clock
>> based on a different timer API than the old kernel. That new timer API
>> may not support the particular chipset on your mainboard correctly.
>
>
Marc Muehlfeld wrote:
> Martin Burnicki schrieb:
>> As a test, you might stop ntpd, then set the system time manually running
>
> # date -u; ntpdate ptbtime1.ptb.de
> Di 16. Okt 09:08:09 UTC 2007
> 16 Oct 11:08:13 ntpdate[2586]: step time server 192.53.103.108
ou have explicitly disabled the feature, either for the first
> setting, or unconditionally, the real ntpd should abort rather than
> stepping more than 1000 seconds.
... unless the -g option has been given on ntpd's command line, which
allowed a large initial offset.
Martin
--
Marti
David,
Martin Burnicki wrote:
> David Woolley wrote:
>
>> In article <[EMAIL PROTECTED]>,
>> Aggie <[EMAIL PROTECTED]> wrote:
>>
>>> But the weird thing is: NTPD will adjust the time on the client half
>>> way between the server and 1970 Jan
my opinion the build environment on the target machine may not be set up
properly. See also:
http://www.google.com/search?q=solaris+%22convenience+libraries%22+%22false+cru%22
Regards,
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
__
from a reference time
source in regular intervals, so it can determine the clock drift by itself
and compensate it. The advantage is that you don't have to measure the
drift manually, and ntpd compensates the drift even if the drift value
changes, e.g. due to temperature changes.
Regards,
Martin
. See also:
>>
http://www.google.com/search?q=solaris+%22convenience+libraries%22+%22false+cru%22
>>
> tnx for all.
> the problem is resolved. the $PATH didn't include the /usr/ccs/bin, so
> the configure script couldn't find the ar.
Thanks for letting us know what
n to work on Vista.
My colleague who maintains the time server monitor will have to check this.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
in the GUI setup during
installation, or simply by editing the ntpd's ImagePath registry key. So it
can easily be disabled to see whether the behaviour changes.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
y a "synchronization lost" message because ntpd resets its internal
filters.
Having a look at the loopstats, and how the offset develops, might give us
more clues ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
and see how ntpd synchronizes. Then
disconnect the cable and connect via WLAN. The router should let your
laptop access the LANTIME either ways, so you can try both and compare how
the offset and jitter figures reported by "ntpq -p" (or in the loopstats)
develop over time.
I'd appr
should
not be required to specify a certain CPU to run on, as proposed by Ryan.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
e other thing that needs to be considered. This is a 64-bit
> system> In that case it's possible that the code may need to be changed
> to deal with it properly. For example using the VS 2005 compiler I have
> found that it uses a 64-bit integer instead of 32-bit integer for
>
any good code you can copy.
>
> I'd start at:
> http://support.ntp.org/bin/view/Main/SoftwareDownloads
> and look in the sntp directory.
AFAIK the code in the SNTP subdirectory has not yet been ported to
Windows ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyr
the Meinberg
>> distribution.
I don't think it would make much sense (or would be even possible) to run a
program compiled for a 64 bit target OS on a 32 bit OS, just because the
hardware is 64 bit.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
David,
David J Taylor wrote:
> Martin Burnicki wrote:
>> While on legacy multiprocessor systems the CPU clocks (and thus the
>> TSC) may differ for each CPU, I'm _assuming_ that multicore CPUs are
>> clocked by the same source, so the TSCs should runs synchrounousl
David,
David J Taylor wrote:
> Martin Burnicki wrote:
> []
>> I've just set up a new test under Vista, so let's see.
>>
>> What I can say right now is that the default tick adjustment value is
>> 156001 instead of 156250 which it used to be on earlier Wind
-p and ntpq -c "rv ..." commands here
then we may be able to help.
And, the versions of NTP on the server and on the clients might be
interesting ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
Hi Ulrich,
Ulrich Windl wrote:
> Martin Burnicki <[EMAIL PROTECTED]> writes:
>
> [...]
>> The test machine is a Intel Pentium D 3 GHz (dual core) with Windows
>> Vista x64. Data of the time synchronization performance was collected by
>> the time adjustment serv
still on holidays until mid December, but I think it's
worth waiting for his comments ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
gt; I do appreciate your efforts with this.
Thanks. We all want NTP to discipline even the Windows system time as good
as possible.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
h
t; Below is some info to help assess my situation, please let me know if
> there's more info I can provide.
Can you tell us which operating systems and which versions of NTP you are
running?
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
_
Martin Burnicki wrote:
> Can you tell us which operating systems and which versions of NTP you are
> running?
Oops, sorry. Didn't see this info at the end of your original message.
Thought below "---" was just a signature.
Martin
--
Martin Burnicki
Meinberg Funkuhre
n different CPUs,
it just tries to run always on the same CPU in order to avoid glitches due
to different TSC values on different CPUs.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
d
which could be used to trigger an interface rescan by udev or similar
whenever an interface becomes available or unavailable.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ntpq -c "rv " ?
I had asked the OP to post the output of the command. However, the output
was truncated. Here's a quote:
> ntpq> rv 8773
> assID?73 status 14 reach, 1 event, event_reach,
> srcadrmaster1, srcport 3, dstadr0.0.0.0,
> dstport 3, leap
The rest of the o
de/english/sw/ntp.htm#ntp_nt_stable
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
in name let's me assume you are located in Germany. Maybe you can
give me a phone call tomorrow so we may have a better chance to see what's
going wrong.
I'll send you my phone number via private mail.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
dows domain and you want to use your own reference time
source without much administrative work then you can either:
1.) install a standalone NTP server and configure the PDC to synchronize to
it
2.) install NTP on a different machine, and let the w32time service on the
DC and all "
the outlyer and thus ignore it. For
redundancy reasons (i.e. if 1 server is temporarily unreachable) the usual
advice here is to configure at least 4 NTP servers.
Regards,
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions m
Folks,
FYI, I've had a phone call with the OP and he told me that the broadcasting
server is in turn a broadcast client of a Windows machine running Tardis.
We've agreed this is a poor setup and the hierarchy should be redesigned.
Martin
--
Martin Burnicki
Meinberg Funkuhren
B
8 MB RAM here can handle more
than 15000 req/sec, i.e. 10 times as much as you need. The relevant HDD
space you need for ntpd depends only on the amount of log files you want to
keep, e.g. the loopstats file and its history.
Martin
--
Martin Burnicki
Meinberg Funku
eresting as my GPS has an offset of -0.173s! Is
> that a coincidence?
I'm sure it does. You might try to "fudge time1" for that particular device,
if the driver supports that.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
e can respond with the time when the
> punchclock requests "net time?" Any assistance would be appreciated.
"net time" uses a NETBIOS call to query the time from another machine. If
you are running a Linux machine then you can enable samba to reply to those
requests.
Marti
Danny,
Danny Mayer wrote:
> Martin Burnicki wrote:
>> Glenn,
>>
>> [EMAIL PROTECTED] wrote:
>>> We use a pc punchclock that relies on the "net time" command. We are
>>> a netware/linux shop and use an ntp time source, however, we do not
>>&
eir clock by an hour or so, punching out and
> leaving. We do not want to offer that temptation.
If you run NTP for Windows here then the times should be synchronized to a
couple of milliseconds. Of course it's a good idea disable time to be
changed by the normal users, as Danny has suggested.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ccasions before (not with Meinberg receivers ;-).
Dave, wouldn't it be a good idea to implement a log message indicating by
which means a leap second announcement has been received? So this could be
traced back to the originally faulty time source.
Martin
--
Martin Burnicki
Meinberg
Unruh wrote:
[...]
> You could just set up ntp to add 33 sec to its time, and you would have
> atomic time.
... until the next leap second occurs.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
que
leap second _is_ a inconsistency of
time.
> At this point I am obligated to use UTC and NTP.
On most Unix-like kernels NTP just passes a leap second announcement to the
OS kernel, and the kernel handles the leap second in the way it is
implemented in the kernel. For details, please see
ht
the past that ntpd thought it had to introduce
a leap second because some bad guy had passed a faulty leap second
announcement. Knowing the source of the announcement would help to identify
the original source of the announcement.
Martin
--
Ma
epends also on the version of ntpd ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
tioned in bugzilla, I'll prepare a patch to fix this.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
nts started up at the same time and had to step,
they wouln't step at the same time, and thus wouldn't do the next iburst
volley at the same time anyway.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing lis
or on the internet. So the settings
used to make ntpd work well for the worst cases could be used if those
cases apply, but the limitations could be reduced in non-worst cases.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
t?
What might be possible is to configure the local NTP daemon to read the
"serial" ref clock via the converter's emulated port. However, this
introduces much jitter since the real communication goes across the LAN
instead directly to the GPS device.
Marti
urce
For a test it is also possible to override the default clock source using a
boot parameter, e.g.:
clocksource=jiffies
You may want to try if some other of the available modules does a better job
in timekeeping. If the active module doesn't work correctly then the
frequency drift often exc
t time. For some
hints how the "best" time source is determined by ntpd, see:
http://www.eecis.udel.edu/~mills/ntp/html/prefer.html
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
time sources may not be appropriate,
and using at least 4 is a better choice.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
noosh wrote:
> Martin Burnicki wrote:
>> Neither the GPS nor the ADAM are NTP servers, so why should a client find
>> it?
> if i do the following
> GPS---> PC(NTP)
> Serial Port
>
> the time is synchronized by GPS.
Right.
hat
certain modules may not work properly on certain chipsets. This must not
necessarily be due to the modules, AFAIK there are also chipsets out there
where the timers don't work properly and would require specific
workarounds.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
ors, and the fact that different clocksource modules
yield different results make me assume that the problems are not with the
base oscillator but with the different types of counters and/or the
implementations of the modudules which use thos specific counters.
See also
http://bugzilla.kernel.org/
nges to the NTP development code base
which shall handle leap seconds on any OS which does not provide a kernel
PLL. I'll still have to check how this code works on Windows, and whether
Dave and my leap second code would now insert 2 leap seconds instead of 1
(I'm afraid this would
lp if i got any wrong
> configuration or i missed something.
Formerly it has been called a bad idea to run Windows as a time server and
Linux as a client. The better configuration would be the other way round.
This is due to the limited resolution of the Windows system clock (16 ms as
mentioned
plausibility check should be for the end of a month.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ave as mentioned there.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
those at the end of March and September. Since the system was introduced in
1972, only dates in June and December have been used."
Up to the recent changes in ntpd (which I have not yet reviewed in detail)
ntpd would indeed have only accepted a leap second at the end of June or
December, which is
day.
Which is the "current" code?
AFAIK the current ntp-stable version 4.2.4p4 still behaves like David
mentiones, but the current ntp-dev version 4.2.5p113 should behave as Bill
Unruh mentiones.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
__
ng on the application.
While UTC is a better choice to use time stamps / calendar dates across leap
seconds (i.e Jan 1 00:00:00 = Dec 1 00:00:00 + (31*86400) TAI is preferred
if correct time _intervals_ are required, even across a leap second.
Martin
--
Martin Burnicki
Meinberg
inberg.de/english/products/tcr167pci.htm
OK, I'm biased ;-) ...
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
27;t you?
The kernel module which lets ntpd use the card as reference time source can
be loaded with a parameter which overrides the real board status and always
tells ntpd the card is synchronized. Just load the module with the
following parameter:
modprobe mbgclock pretend_sync=1
Of course this p
w32time on the domain
controller.
You should not let real NTP clients use w32time as time source, though.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
in the offset and
> jitter columns? What makes a "good server" in terms of ntpq -p output?
> Low offset? Low jitter? Some combination?
Depending on what causes the jitter and offset. If timekeeping by the kernel
is poor the this may also cause high jitter and
it better than 1 microsecond accuracy.
However, though some of the Windows API calls provide a resolution of 100
nanoseconds those API calls return exactly the same time stamps betwween 2
timer ticks, and then the returned time steps by the amount of the timer
tick interval.
Martin
--
Martin Burnicki
Danny Mayer wrote:
> Martin Burnicki wrote:
>> Though it's normally preferable to run ntpd rather than w32time, there is
>> a limitation if you run ntpd on a domain controller:
>> The domain members (workstations) will stop detecting the domain
>> controller aut
mentioned that w32time may sometimes be the preferred solution.
I'm not familiar with W2k domain management, so I wonder whether the group
policied could also be used if ntpd was running on the PDC.
Please see also my reply to Danny.
Martin
--
Martin
Andrew,
Andrew Hodgson wrote:
> On Fri, 22 Feb 2008 09:31:38 +0100, Martin Burnicki
> <[EMAIL PROTECTED]> wrote:
>>Though it's normally preferable to run ntpd rather than w32time, there is
>>a limitation if you run ntpd on a domain controller:
>>The doma
ead to do the DNS lookups (except
the special Windows things, which have already been implemented as
threads).
There are no special requirements except for blocking critical sections
while some parameters are updated.
This would also simplify a fix for bug #987: http://bugs.ntp.org/987
Martin
--
Ma
DIT) under HKLM\CurrentControlSet
>> \Services\w32time:
>>
>> [TimeProviders\NtpClient]
>> InputProvider=DWORD:0
>> [TimeProviders\NtpServer]
>> InputProvider=DWORD:0
>>
>> This will cause NTP to start before W32TIME and thus NTP will take
>> over discip
rk I don't think that's a proper solution.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
ng on www.microsoft.com. If
I start searching at support.microsoft.com the search returns no results,
which is pretty poor (for MS).
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
Evandro Menezes wrote:
> On Feb 26, 2:57 am, Martin Burnicki <[EMAIL PROTECTED]>
> wrote:
>>
>> Of course they still can't both open port 123, so the result should be
>> what David Wooley has mentioned in his reply.
>
> No, but the workstations use an RPC
Danny,
Danny Mayer wrote:
> Martin Burnicki wrote:
>> I have recently received a note from someone who seemed to be very
>> familiar with Active Directory. That person told me whn w32time starts it
>> makes an entry in the LDAP directory which tells the clients at logon
&
Danny Mayer wrote:
> Martin Burnicki wrote:
>> I've mentioned in my earlier post that the entry is supposed to be in the
>> LDAP tree. Why should this be in DNS? Directory services have been
>> designed to as a database to keep track of objects and attributes of
>
Maarten,
Maarten Wiltink wrote:
> "Martin Burnicki" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> [...]
>> I guess a Windows domain would work without a local DNS since the names
>> of the Windows machines could also be resolved by the WIN
> But when the workstations contact the DC, I think that NTP will
> reply instead.
If that setup really works then it's indeed a good workaround for using ntpd
on the PDC.
Unfortunately I've currently no W2k3 domain set up for tes
ld already do so.
Does someone know how this is handled by other protocols using multicast,
e.g. SLP or mDNS?
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
Danny Mayer wrote:
> Martin Burnicki wrote:
>> Danny Mayer wrote:
>>> John Vossler wrote:
>> [...]
>>>> My initial reaction to this issue was to determine if there was an OS
>>>> (Solaris) directive to include the multicast for other interfaces i
So your comments make things much
clearer.
Thanks,
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
look at it.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
Frank,
thanks for that crash course on the details of multicasting which makes
things much clearer.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman
I didn't see
the obvious solution. Since the patch has not yet been committed I'll
update it once more.
Thanks,
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
https://lists.ntp.org/mailman/listinfo/questions
> the "pool" configuration line seems to be non-functional. Details
> below:
[...]
The keyword "pool" has been introduced in the development branch of NTP
(ntp-dev, v4.2.5), so it is not supported in ntpd v4.2.4p4 which is the
current "stable"
Ryan Malayter wrote:
> On Mar 4, 10:29 am, Martin Burnicki <[EMAIL PROTECTED]>
> wrote:
>> The keyword "pool" has been introduced in the development branch of NTP
>> (ntp-dev, v4.2.5), so it is not supported in ntpd v4.2.4p4 which is the
>> current "
n crond performs its tasks.
What tasks are specified in cron.weekly?
Could you run them one by one to see which one produces the time slew?
Do you also observe time slews if you run other tasks which cause much disk
and/or network I/O?
Martin
--
Martin Burni
back index documenting when changes
> have been introduced other that the rather vague release notes.
I think this is OK as long as it's made clear that this documentation refers
only to the current development code.
Anyway, I'd appre
s a Meinberg FAQ which tells how to fix those brokeen Windows
clients and let them send normal peer requests instead of symmetric active
requests:
"Why does my Windows Time Service (w32time) not synchronize with my NTP
Server?"
http://www.meinbe
ght again, and basically this is a good thing. However it's even hard for
people who are loosely involved in the development to keep track of when /
in which version new features become available, and it's even much harder
for those who are "just" users of NTP.
So there&
1 - 100 of 691 matches
Mail list logo
