| Re: [chrony-users] Many servers became unreachable |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Many servers became unreachable
- From: Roel Schroeven <roel@xxxxxxxxxxxxxxxxx>
- Date: Tue, 02 Jun 2015 11:01:43 +0200
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=roelschroeven.net; h=content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=k6AC4fP2U76p3fPZwcwUh78TERg=; b=fBhgsA QEtcKGdbFqQohI6+AzWcgPFWSwncKYCJ61wSBYVQgVOjIv4GP4Fyt07j3rtJE8xe IBS8uCqZQNMo9mmAL4y+rN/Uh5Tr2OGVqUh0yJDzLGr3Sp4KQJ6jTf3CGIllP1Uq n+aO8Bm2T0abBgfWfZBe4bB9tMXOcmbaqYo+A=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=k6AC4fP2U76p3fP ZwcwUh78TERg=; b=gmXUf7CB3fsZgWQFpVz6US/ONhLl4XK8uCnoHDMlFRRtYUd IYN2WZcXyfptMydv+QXgOet7IR+iNrsuJJGaBjrP01bbsLFUF/qhx/hSMEqIKuTy q2amTeIkwSKU/FQsFt2xlKV3N/664WSdFpTKxVsCICQjwf7FtTaMKIDXPw/o=
Miroslav Lichvar schreef:
# /usr/sbin/chronyd -Q 'acquisitionport 122' 'server ntp1.telenet-ops.be iburst'
A question about the acquisitionport option: if I'm reading to the
documentation on my system (old chrony version) correctly, it only
affects the rapid-fire measurements requested with the initstepslew
directive. The current documentation on the website doesn't mention
initstepslew, implying that acquisitionport affects all server
communication.
Has its behavior changed, or am I reading the documentation wrong?
Best regards,
Roel
--
"Life ain't no fairy tale
Just give me another ale
And I'll drink to Rock 'n Roll"
-- Barkeep (The Scabs)
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.