| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Ensure consistent marking of '(void)' for most normal usage of fprintf()
TESTED:
'scons build-all check' passes
Signed-off-by: Fred Wright <fw@fwright.net>
|
| |
|
|
|
|
| |
I sure hope I did not drop a zero anywhere...
|
|
|
|
|
|
| |
ntpshmmon.c:34:5: warning: implicit declaration of function 'memset'
ntpshmmon.c:34:5: warning: incompatible implicit declaration of built-in
function 'memset'
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changing the output format without bumping the version number was wrong.
Changing the output format without fixing the documentation and
examples (in INSTALL and elsewhere) was wrong.
Removing the 'sample' keyword at the beginning of the line was wrong.
It broke contrib/ntpshmviz. More generally, it broke the property
that the format was self-describing and extensible.
Removing the comment leader on the second line was wrong. That meant
parsers for the format, such as the one in contrib/ntpshmviz, would
try to interpret the header as data and throw errors.
|
| |
|
|
|
|
| |
No point polling the system clock when the result is not used.
|
|
|
|
| |
Stop reading time that is just going to be thrown away.
|
|
|
|
|
| |
Many thanks to Nuno Gonçalves <nunojpg@gmail.com> for clarifying the
problems in ntpshmmon.
|
|
|
|
|
|
| |
ntpshmmon no longer prints duplicates
ntpshmmon can now work with 5Hz PPS
removed no longer needed -c (cycle time) option
|
| |
|
| |
|
|
|
|
|
| |
Plus a logical reordering of things so more timespec stuff is in
timespec.h
|
|
|
|
|
|
|
|
|
| |
Timespec is a 62 bit number, it does not fit in the 32 bits of
a long. Use 'long long' instead. 'long long' is always at least
64 bits long and is the same as a native int when compiled as 64 bit.
Note that many 64 bit OS still run 32 bit binaries, and many small
devices like RasPi's are 32 bit.
|
|
|
|
| |
Timespec is a 62 bit quantity that does not fit in a 32 bit long.
|
|
|
|
| |
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
| |
|
| |
|
|
|
|
| |
All the clocks look alike...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proximate cause was that we've been seing emission of error
messages that were randomly and disturbingly variable across different
environments - notably Raspbian and Gentoo splint gave nontrivially
different results than Ubuntu 14.10 splint. And this was *not* due to
Ubuntu patches! A pristine splint built from the 3.1.2 tarball on
Ubuntu didn't match the Raspbian and Gentoo results either.
But this has been coming for a while. Easy access to more modern
static analyzers such as coverity, scan-build and cppcheck has been
decreasing the utility of splint, which is unmaintained and somewhat
buggy and not easy to use.
Only file not cleaned is ppsthread.c, because Gary has been working
on it during this cleanup.
All regression tests pass. PPS observed live on GR601-W.
|
|
|
|
|
| |
...no attempt to address the weird cross-platfprm variability we've seen lately.
All regression tests pass.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
All knowledge of the ntpd SHM format is now confined to the three
files ntpshm.h, ntpshmread.c, and ntpshmwrite.c.
No logic changes. All regression tests pass. PPS works on GR-601W.
|
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
|
All regression tests pass.
|