Dear list members:
I have used ntpd in the past. I am now working with chronyd on Centos
7.3 which has v 2.1.1
For allowing local hosts to query my ntpd server I would use:
restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap
In the chronyd docs I only see the following equivalent:
al
This is on Centos7 on arm:
In my continuing journey to run a armv7 server with no battery clock, I
have been strongly advised on the postfix list that it should NOT start
until the system time is after the create time of the running version of
postfix.
/usr/lib/systemd/system/postfix.service
On 04/20/2017 01:03 PM, Miroslav Lichvar wrote:
On Thu, Apr 20, 2017 at 12:33:29PM -0400, Robert Moskowitz wrote:
This is on Centos7 on arm:
In my continuing journey to run a armv7 server with no battery clock, I have
been strongly advised on the postfix list that it should NOT start until
On 04/21/2017 03:26 AM, Miroslav Lichvar wrote:
On Thu, Apr 20, 2017 at 03:42:24PM -0400, Robert Moskowitz wrote:
On 04/20/2017 01:03 PM, Miroslav Lichvar wrote:
The -s option would help with that, but the improved behavior which
restores time from the driftfile when there is no RTC was
Gaining understanding...
On 04/21/2017 06:21 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 05:59:12AM -0400, Robert Moskowitz wrote:
I was looking at the man for chronyd, and saw that the man for 2.1.1 says it
uses the drift file:
If chronyd doesn't support the R
On 04/21/2017 08:35 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 08:26:31AM -0400, Robert Moskowitz wrote:
On 04/21/2017 06:21 AM, Miroslav Lichvar wrote:
However, you could force chronyd to ignore the RTC by setting
rtcdevice to a nonexistent device and always use the driftfile, e.g
On 04/21/2017 02:03 PM, Bill Unruh wrote:
On Fri, 21 Apr 2017, Robert Moskowitz wrote:
Gaining understanding...
On 04/21/2017 06:21 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 05:59:12AM -0400, Robert Moskowitz wrote:
I was looking at the man for chronyd, and saw that the man for
Miroslav,
I have been following your thread on chrony 3.1 coming out in Centos 7.4.
How does this impact the hacks we did to deal with no battery rtc on
many arm boards?
thanks
On 04/21/2017 08:35 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 08:26:31AM -0400, Robert Moskowitz wrote
I an setting up a Fedora 26 image on a Cubieboard, not battery RTC.
F26 has v 3.1:
chrony-3.1-4.fc26.armv7hl.rpm
On my Centos7 systems with Chrony 2.1.1, I have had to:
cat /etc/chrony.conf || exit 1
rtcdevice /dev/doesnotexist
EO
Back some time ago, I was dealing with an old version of chronyd in
Centos (my notes say 2.1.1) and working with armv7 boards lacking RTC
battery. The hack was to add:
rtcdevice /dev/doesnotexist
There was somewhere a message (that I cannot find) that indicated this
would be better supported
One thing is to use the timestamp from the drift file with:
cat
For Centos/Fedora I would be looking at the systemd service file for
chronyd (along with the /etc/system file I mentioned), but I do not know
how Debian flavors manage services.
On 1/4/19 2:00 PM, Catherine Newman wrote:
Thanks very much Miroslav & Robert - I find the little things just
help
12 matches
Mail list logo
