[chrony-users] chrony-3.4 bug?

["LeBlanc, Daniel James" <daniel.leblanc@xxxxxxxxxxxxx>]

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?

 

Thanks.

 

Dan LeBlanc