ine by 0.02 to get the
mean offset close to zero. When the NTP source is offline, your clock
synchronized to the GPS source should be accurate to about 10
milliseconds.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subj
merQueueEntry *) 0x0
Hm, there should never be NULL in the next field.
Is it reproducible? Can you please attach your config file?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users
onyc
and chronyd bind to 0.0.0.0 by default, so it's up to kernel to do
the right thing.
Adding "bindcmdaddress 127.0.0.1" to chrony.conf might force
chronyd to reply from 127.0.0.1.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubs
On Thu, Apr 08, 2010 at 01:37:13PM +0530, J. Bakshi wrote:
> On 04/06/2010 01:19 PM, Miroslav Lichvar wrote:
> > Adding "bindcmdaddress 127.0.0.1" to chrony.conf might force
> > chronyd to reply from 127.0.0.1.
>
> Ok, adding the config and now I get
>
> ``
cy and
offset reported in tracking.log), please send me "uname -s -m" output
and I'll add it to the configure script.
Thanks,
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-user
gt; addressing.h:45: error: expected specifier-qualifier-list before 'uint32_t'
> addressing.h:48: error: expected specifier-qualifier-list before 'uint16_t'
Try with gmake instead. I think the only native BSD make that works
with the Makefile is on NetBSD.
--
Miroslav Li
#include line is removed from sysincl.h?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
iers or '...'
> before 'size_t'
> /usr/include/kvm.h:86: error: expected declaration specifiers or '...'
> before 'pid_t'
Ok, please add
#include
before
#include
in sys_sunos.c.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@c
SHM
refclock driver.
I posted recently a chrony+gpsd+LinuxPPS howto here:
http://ml.enneenne.com/pipermail/linuxpps/2010-June/003894.html
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-req
0310y +0ns[ +0ns] +/-0ns
Do you get anything when the segment 0 (message decoded
timestamps) is used instead?
That would mean the communication between gpsd and chrony is working,
but gpsd doesn't provide the PPS timestamps.
What is the output from gpsd -n -N -D 6 /
seem to be any messages related to PPS in the log. Is the
PPS wire connected to the DCD pin?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
onyc sources and sourcestats output
* Add reselect command to force reselecting best source
* Add -m option to allow multiple commands on command line
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For he
rmer provides only
subsecond time information, it needs another source to get the missing
seconds. The PPS samples received by SHM refclock are already paired
with NMEA messages and completed in gpsd, so using only the SHM 1
refclock alone is perfectly fine and I'd say maybe even recommende
col, which means that to get PPS samples
with nanosecond resolution the PPS refclock won't be necessary.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@ch
On Mon, Mar 21, 2011 at 06:33:33PM +, Ed W wrote:
> On 21/03/2011 17:37, Miroslav Lichvar wrote:
> > BTW, the soon to be released gpsd supports kernel PPS timestamping and
> > also the chrony SOCK protocol, which means that to get PPS samples
> > with nanosecond resolu
g
> >> (They also have a 20hz GPS with decent sensitivity and a GPS/GLONASS
> >> hybrid board...)
> >
> > And exactly what would a 20Hz buy you?
20 times more samples could improve the stddev of the calculated mean up to
factor sqrt(20). It would also allow shorter po
x policy includes a chrony
policy.
I don't know anyone running chrony in the pool.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
than a sw delay? I
think with GPIO the interrupts go straight to the CPU, reducing the
delay significantly.
> For a cheaper version, get the sure GPS board. It is supposed to give about
> 20ns timing on the PPS line, rather than garmin's 500-1000ns
Someone reported on the ntp list that Gar
good to ask what they think about using chrony
on the p...@lists.ntp.org list.
http://www.pool.ntp.org/en/join/configuration.html
The code that does the monitoring and rejects bad servers from the
pool is available here (see the pool script):
https://github.com/abh/ntppool
--
Miros
rinfo() return a permanent error instead of temporary.
- update documentation a bit
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
umed to be 100 or a power of 2.
> Note, seems to be working fine without any config stanzas, I just thought it
> curious?
Yes, keep it at 100 :).
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject
imple though, so not that desirable)
Ok, that shouldn't be hard.
> 2) lpj offset adjustment when re-reading tracking data...
Hm, I'm not sure chrony should know anything about clock sources and
their calibration. Is the lpj value available in /sys, or just dmesg?
I think
d TSC clocksource calibration: 3191.999 MHz
The second value didn't change after reboot and chrony's drift stayed
the same too!
It seems to be this commit, merged just few months ago.
http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=08ec0c58fb8a05d3191d5
On Wed, Apr 06, 2011 at 10:58:24PM +0200, Miroslav Lichvar wrote:
> I just made a test with a 2.6.38-rc0 kernel
That should have been 2.6.39-rc0. But it should be in 2.6.38 too.
$ git describe --contains 08ec0c58fb8a05d3191d5cb6f5d6f81adb419798
v2.6.38-rc1~480^2~1
--
Miroslav Lichvar
---
has no PM or HPET timers so I think
> this is unlikely to help *my* specific case, but it's very good news in
> general!
Does it work for you? Or were you able to get the drift recalculation
working?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.o
call. Chrony
doesn't do that.
> If there is going to be a fix, it should be within gpsd, and not within chrony
> or ntpd.
I agree, it could be a database of delays for known broken GPS
units/firmwares.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfam
fine, as long as a recent gpsd version is used.
I think versions before 2.90 didn't pair the NMEA and PPS samples and
needed chrony/ntp to sync first to the NMEA source and only then it
would start sending the PPS samples.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@
lution.
If you don't want that, you can recalculate the frequency offset in
the drift file before chronyd is started, according to the current and
previous lpj.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject
ernel version fixing the problem, I think I've
always had it. Maybe it's not possible to get better resuls from
250ms measurement interval. The hpet and acpi_pm clocksources don't
seem to have this issue.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfami
r production use.
Since 1.25-pre1, the following changes were made:
* Use system headers for Linux RTC support
* Add include directive
* Add reselectdist command
* Fix crash due to instability in calculation of sample weights
* Various minor bug fixes and improvements
--
Miroslav Lichvar
---
To u
n_done = 0;
>
> while ((n_timer_queue_entries > 0) &&
> (UTI_CompareTimevals(now, &(timer_queue.next->tv)) >= 0)) {
This while was replaced with if to avoid such loop, but that was
before 1.24, did you see the problem with 1.24 or later?
--
Mirosl
ould test something.
Are the patches or your git repo publicly available? Maybe some of
them should be included?
Thanks,
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@
is), and (iii) that it was not synchronised
> too long ago
> */
Which of the three conditions fails? Perhaps it's the same problem as
in the acquire module?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in
25 years in future and the check fails. If the timestamps were
compared in NTP timestamps, the NTP_MAXAGE check would fail instead.
RFC 5905 doesn't have the NTP_MAXAGE check. Interestingly, in ntpd it
seems there is no reftime checking at all, I'll have to ask on the ntp
list which is co
Chrony 1.25 is now available via the "Download" page at
<http://chrony.tuxfamily.org>.
Since 1.25-pre2, there was only one change which improves the
accuracy in certain network conditions.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
w
l between the two
hosts which is dropping the NTPv3 packets as they don't match the
version in the requests.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.
should reply with
the correct address.
Thanks,
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
On Mon, May 09, 2011 at 02:47:22PM -0600, Bauer, Steven J. wrote:
> Let me know if you need me to test anything, etc.
The latest git should now work with multiple IPv6 address, please let
me know if it doesn't. Thanks.
--
Miroslav Lichvar
---
To unsubscribe email chrony-us
ency on start without drift file
* Add waitsync command
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
Chrony 1.26 is now available via the "Download" page at
<http://chrony.tuxfamily.org>.
Since 1.26-pre1, there was only one change which enables the
--enable-forcednsretry configure option by default.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tux
> P.S. Can we call it chrony 2.0 yet?
There are still some features like NTPv4 support or clock combining
that I think would be good to have before making a major version bump.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsu
e.
> > There are still some features like NTPv4 support or clock combining
> > that I think would be good to have before making a major version bump.
>
> OK, so how about 1.3?
1.3 is smaller than 1.26.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chron
ox 15:00BST today?
>From the three new samples in measurements.log I don't see any
difference :). I may be too far to see it.
--- 91.220.24.240 ping statistics ---
142 packets transmitted, 142 received, 0% packet loss, time 141200ms
rtt min/avg/max/mdev = 30.401/33.867/52.063/4.082 ms
--
Mi
made. I suspect one of the sourcestats asserts which check for
samples from future would fail here. Of course, chronyd should just
ignore an invalid dump and not crash.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subje
ng about that ?
Can you confirm it was the -s option that was causing the crash?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help&q
u get my email about the necessary additional CFLAGS to make RTC
> access working with chrony 1.2.6 using Linux kernel 2.6.27.48 ?
I've seen it mentioned in this thread. It seems to be a problem with
the system headers on your system, we no longer maintain a local copy
in our sources.
--
Miro
her initialization) is completed, successfully or
unsuccessfully.
Why do you need a terminal to run chronyc?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...
that does that mean when "chronyd -s" returns,
> the "initstepslew" will have taken place already ?
Yes, also the clock should be set from RTC with -s and all sockets are
ready, so chronyc (or gpsd) can immediately connect.
--
Miroslav Lichvar
---
To unsubscribe email
n if I have 3 valid NTP servers (setup with a valid ,
> and "SU-Server3") I see the "can't synchronize" message a lot.
Is stratum for the third server 3 or higher? The sources output might
help.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
000 2000.000 +0ns 4000ms
Something is wrong, the skew values are extremely high. Usually, it's
just couple ppm.
Is the client running in a virtual machine?
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in
requency?
What clocksource does it use?
cat /sys/devices/system/clocksource/clocksource0/{current,available}_clocksource
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@ch
n to all servers so chrony
doesn't touch the clock and see if the skew values get better.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
em to me privately. If I see anything interesting I'll
post it here.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help&qu
d in the test without the application running and the
test with noselect. Posting the sourcestats output after chrony has
been running for at least 15 minutes should give us enough
information.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with
@@ get_version_specific_details(void)
if (kernelvercmp(major, minor, patch, 2, 6, 27) < 0) {
have_readonly_adjtime = 0;
} else {
-have_readonly_adjtime = 1;
+have_readonly_adjtime = 0;
}
/* ADJ_NANO support */
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-req
7a855174e3b53d182b97a26b2e27a29726a1
It's not that the readonly adjtime is not supported (it's actually
since 2.6.24), but it randomly sets the PLL offset. This seems to be
fixed in 2.6.28.
I'll change the condition to use it only with 2.6.28 and later.
Thanks,
--
Miroslav Lichvar
show that it's not the case:
$ grep ctxt /proc/`pidof chronyd`/status
voluntary_ctxt_switches:307234
nonvoluntary_ctxt_switches: 2134
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help ema
e application
that it's not able to measure the offset properly.
Another test could be to compare the stability of the RTC and system
clock. The adjtimex tool has -c option which prints differences in
frequency between the two clock measured over short intervals. If the
error is n
the after trim
offset measurement can finish.
Thanks for the report.
BTW, writertc is done automatically when chronyd is stopped by
SIGTERM.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For he
with the servers specified in chrony.conf. The chronyc client
resolves the server name on its own before sending the command to
chronyd to add the server and it gives up immediately on resolving
error. You'll probably need to wrap the chronyc call in a loop and
retry unti
.
> refclock SOCK /dev/gps
This should be /tmp/chrony.ttyS0.sock or /var/run/chrony.ttyS0.sock,
but probably not related to your problem.
--
Miroslav Lichvar
---
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chr
ore 2.6.28
* Changed chronyc protocol, incompatible with older versions
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help"
ered sample (- in raw offset) could be
perhaps interpreted as a jitter divided by some small constant.
The tracking log is more about the local clock and the statistics log
is from already filtered data from refclocks.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tu
prevent the PPS source (which is "lock"ed to the GPS source) from
> working. IMO this could use expanding in the user guide.
Patches for the documentation are very much appreciated :). There are
some other areas which needs update, for instance the section with
server name
On Tue, Aug 21, 2012 at 10:53:31AM +0100, Tomalak Geret'kal wrote:
> On 21/08/2012 10:24, Miroslav Lichvar wrote:
> >There are some other areas which needs update, for instance the
> >section with server name resolving on start is no longer valid, as
> >chrony wil
mly and then vanish
> when I replace the binary with a new build which differs only by
> more verbose syslog output; to me, this screams UB in my build, but
> yikes. My investigation continues...!
That sounds like a race condition. Does it work under strace?
Does flushing the kernel cache tri
check for the CAP_SYS_TIME
capability which root should always have (IIRC filesystem capabilities
were not supported yet). Any chance the binary could have the suid bit
set?
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe"
.
That would be pretty hard to do in the current code. Also, some parts
of the config are evaluated under root (refclocks, port binding) and
can't be changed after the permissions are dropped.
How can killing chronyd fail? If the daemon doesn't respond to the
signal, will reloading w
et it to capture asserts and the other to capture clears, the one
started earlier wasn't getting any events.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
these problem would probably be using an async
DNS library which returns the TTL. But I didn't find a good one the
last time I checked. I think it should be small, well maintained,
GPLv2 compatible and available also on other systems than Linux. Any
tips?
--
Miroslav Lichvar
--
T
has to be done in
nscd or a local DNS server.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
nanoseconds in SHM refclock
* Make transmit timestamps random below clock precision
* Fix crash and hang with RTC or manual samples
--
Miroslav Lichvar
pgpZgUgxpvBnQ.pgp
Description: PGP signature
nts will no longer accept its time.
> By the way, what happened to the gmane mailing list subscription?
> The last mail on gmane is from 2009...
That's probably when we moved the lists to tuxfamily.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
On Fri, Mar 08, 2013 at 03:07:04PM +0100, Miroslav Lichvar wrote:
> > By the way, what happened to the gmane mailing list subscription?
> > The last mail on gmane is from 2009...
>
> That's probably when we moved the lists to tuxfamily.
I've sent an email to the gman
unless its servers are
down too).
If all of your computers share the same link to the internet and each
of them is configured to use multiple servers (e.g. from pool.ntp.org),
using the peer option between them probably won't make a difference.
--
Miroslav Lichvar
--
To unsubscribe
in the config (makestep 1 -1
to not limit the step to the first update) or chronyc makestep.
The chronyc tracking output prints the remaining uncorrected offset.
(I'm wondering if it would be useful to include it also in the
tracking log.)
--
Miroslav Lichvar
--
To unsubscribe email chron
>
> I believe it became invalid by this mechanism in acquire.c:
Thanks for the detailed report and the patch. I will push it to git
and it will be in the next release.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the s
duplicated initstepslew address
* Fix delta calculation with extreme frequency offsets
* Set local stratum correctly
* Remove unnecessary adjtimex calls
* Set paths in documentation by configure
--
Miroslav Lichvar
pgpMX_ytIu6Kl.pgp
Description: PGP signature
as actually performed
after the sources were set online, you will need to check the time
stamps in tracking log or check if the Ref time field in the tracking
report has changed.
Does this answer your question?
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with
I expect some "Makestep OK" message? or it's a different state?
Not in the tracking log, but in the system log there should be a
"System clock was stepped by x seconds" message.
>From the number of columns in your tracking log it seems it's an older
version of ch
:
* Treat address bind errors as non-fatal
* Update chrony.spec
--
Miroslav Lichvar
pgpYwnN9iSdP_.pgp
Description: PGP signature
and they require the client to be authenticated since version 1.25.
--
Miroslav Lichvar
pgpzK2WIFy0ed.pgp
Description: PGP signature
ce ID)
and the remaining offset correction (the System time field in the
output).
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
l from git, run configure with --enable-trace, recompile and
see what refclock messages do you get?
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
noselect option to the GPS and PPS sources
(without any locking) and observe the offset values in the refclocks
log or chronyc sourcestats output.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help ema
ellites in
> view, otherwise I don't have a great explanation for the wander seen in the
> ntp plot.
>From what I remember from other discussions about NMEA timing, it
mainly depends on how is the firmware implemented and the number of
visible satellites may have nothing to d
On Thu, Nov 28, 2013 at 11:11:18AM -0800, Bill Unruh wrote:
> On Thu, 28 Nov 2013, Miroslav Lichvar wrote:
> >That looks similar to what I see with with a Garmin 18x LVC. This is a
> >capture 30 hours long I did some time ago (the NMEA source's offset
> >value wa
ly better to use the noselect
option or don't configure it at all.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
sp=0.022734546
They are ignored in a different place because the lock option
wasn't used this time.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
terval used in the source
selection algorithm, so increasing the value from 0.01 to 0.4 or
larger should fix the problem.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony
On Wed, Dec 11, 2013 at 10:11:48AM -0800, Bill Unruh wrote:
> On Wed, 11 Dec 2013, Miroslav Lichvar wrote:
> >When no source is selected, the PPS samples are ignored. If the SHM
> >source doesn't move to the acceptable range to overlap with the PPS
> >source in 8 polling
g interval, so that the frequency
observed in the NTP time changes slowly and the clients can stay in
sync during the whole correction.
At this moment, I'm not sure how difficult it would be to implement
in chrony.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.t
On Tue, Dec 03, 2013 at 10:43:09AM -0800, Bill Unruh wrote:
> On Tue, 3 Dec 2013, Miroslav Lichvar wrote:
> >I think a better solution to this problem would be an approach similar
> >to the Google's NTP leap second smearing. The jump in time is smeared
> >with a cosi
On Wed, Dec 04, 2013 at 12:46:10PM -0800, Bill Unruh wrote:
> On Wed, 4 Dec 2013, Miroslav Lichvar wrote:
> >With the cosine smear, the frequency offset changes slowly (small
> >wander), but can reach a large absolute value.
> >
> >If I calculate right, it can corrrect
problem with NTP clients not supporting
different NTP port.
How close stayed the clients in your test?
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chro
= (double)(1UL << shift_hz);
basic_freq_scale = dshift_hz / dhz;
nominal_tick = (100L + (hz/2))/hz; /* Mirror declaration in kernel */
- slew_delta_tick = nominal_tick / 12;
+ slew_delta_tick = nominal_tick / 2500;
max_tick_bias = nominal_tick / 10;
tick_update_hz = hz;
--
Miro
On Thu, Dec 05, 2013 at 10:34:22AM -0800, Bill Unruh wrote:
> On Thu, 5 Dec 2013, Miroslav Lichvar wrote:
> >In this example I think clients running chronyd would stay together
> >within 1 second during whole operation even with 1024s polling
> >interval.
>
> That is w
On Fri, Dec 06, 2013 at 09:36:52AM -0800, Bill Unruh wrote:
> On Fri, 6 Dec 2013, Miroslav Lichvar wrote:
> >Well, I tried it in the clknetsim simulator. Two chrony clients were
> >synchronized to a chrony server, the clients were started 512 seconds
> >apart and they w
27;m looking for already
> exists, but not enabled at the times I want.
With the local stratum active, it still servers the estimated NTP
time. As there are no sources, the NTP time will be close or equal
to the raw system time.
> The maximum error between clients is 1 second.
That's pl
would be:
port 0
bindcmdaddress 127.0.0.1
bindcmdaddress ::1
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.
1 - 100 of 1070 matches
Mail list logo
