| Re: [chrony-users] chrony-3.4 bug? |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
On Wed, Oct 31, 2018 at 11:55:29PM +0000, LeBlanc, Daniel James wrote:
> Hi All.
>
> I have discovered that chrony-3.4 will not startup on RHEL 7 if I pass it the -n option. It times out. My executable start string is as follows:
>
> /var/chrony/sbin/chronyd -4 -u chrony -f /var/chrony/etc/chrony.conf -l /var/chrony/log/chrony.log
>
> If I add the -n after the -4 or replace the -4 with -n, chronyd fails to start. Has anyone else successfully used the -n flag?
It doesn't start as a systemd service? Can you please post the chrony
unit file and chrony config?
There was one change in chrony-3.4 that could be related. The default
pidfile has moved from /var/run to /var/run/chrony. So, you may need
to update the unit file or chrony config.
--
Miroslav Lichvar
--
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.