Hi Neels and Tom,
On Fri, Jun 16, 2017 at 08:20:35PM +0200, Neels Hofmeyr wrote:
One point may be that it's not a very powerful
machine: an APU with an 800MHz
dual core.
That actually means: An AMD Embedded G-Series T40E APU. We like to
use passive cooled, low-end processors whenever possible.
If clock skew
is not occurring at startup, then process scheduling is
probably related. If the flow of CLK IND stops entirely, as in the case when
osmo-trx stops running, the message would be "No clock from osmo-trx". Clock
skew could also occur because of variability in calling gettimeofday(), but I
have not encountered that on any systems that I run.
With NTP switched off I have no idea why the system clock could jump around. I
also looked in the root crontab and so on, maybe something is still calling
ntpdate on that system...
you can always run a tcpdump on the ntp port, if you're worried about
that.
--
- Harald Welte <laforge(a)gnumonks.org>
http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)