Ivan Shmakov wrote:
I wonder, how do I configure ntpd(8) (as of the Debian Wheezy
ntp package [1]) /not/ to touch the hardware clock?
ntpd does not set the hardware clock. That is done by the Linux kernel,
when the clock is disciplined by anything.
It's a long time since I
I wonder, how do I configure ntpd(8) (as of the Debian Wheezy
ntp package [1]) /not/ to touch the hardware clock?
[1] http://packages.debian.org/wheezy/ntp
--
FSF associate member #7257 http://sfd.am-1.org/
___
questions mailing
David Woolley david@ex.djwhome.demon.invalid writes:
Ivan Shmakov wrote:
I wonder, how do I configure ntpd(8) (as of the Debian Wheezy ntp
package [1]) /not/ to touch the hardware clock?
ntpd does not set the hardware clock. That is done by the Linux
kernel, when the clock is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Colleagues,
Upgraded to ntpd 4.2.7p303 from p295 two days ago and twice now it has
died unexpected with the following error:
12 Sep 23:40:26 ntpd[83434]: 86.47.187.7 local addr 172.16.2.10 - null
12 Sep 23:40:48 ntpd[83434]: ntp_monitor.c:136:
On Wed, Sep 12, 2012 at 02:28:24PM +0200, Ulf Samuelsson wrote:
Anyone knows if there are any available Linux based S/W to test the
throughput of NTP servers?
I.E:
packets per second?
% of lost packets
etc?
I've used tcpdump and tcpreplay to measure the maximum packet
Ron Hahn writes:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Colleagues,
Upgraded to ntpd 4.2.7p303 from p295 two days ago and twice now it has
died unexpected with the following error:
12 Sep 23:40:26 ntpd[83434]: 86.47.187.7 local addr 172.16.2.10 - null
12 Sep 23:40:48
