| Re: [chrony-users] Setting up Chrony with PPS |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324
UBC, Vancouver,BC | Program in Cosmology | unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/
On Fri, 19 Feb 2016, Deven Hickingbotham wrote:
Miroslav,
After installing 2.3 the 1.24 files remain.
v2.3:
/usr/local/bin/chronyc
/usr/local/sbin/chronyd
looks for /etc/chrony.conf, but not installed
v1.24
/usr/bin/chronyc
/usr/sbin/chronyd
/etc/chrony/chrony.conf
/etc/chrony/chrony.keys
The problem is that you or your system could get confused. If /usr/local/bin
is ahead of /usr/bin (and similarly for sbin) then it will grab the new one
first. Alternatively put /usr/local/sbin/chronyd and /usr/local/bin/chronyc
anywhere and anytime you want to run them, and in any script tht wants to run
them (systemd, /etc/init.d,...)
/etc/chrony.conf and /et/chrony/chrony.keys should be fine.
So is it correct to assume that I have to delete v1.24 chronyc and chronyd
and move the v1.24 chrony.conf and chrony.keys files to /etc?
You can if you wish.
Will the boot up process recognize the new file locations?
You have to tell it.
In order to get PPS to work with ntp, I had to make the following changes and
wondered whether chrony would need something similar?
1. To /boot/config.txt add dtoverlay=pps-gpio,gpiopin=4
I do not know what that is, but probably it is good to leave that in. It is
probably what creates /dev/pps0 tied to the gpio.
2. To /etc/modules add pps-gpio
yes
Deven
--
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.
--
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.