search for: chronyd

This is for centos 7 that has chronyd 2.1.1 I am looking into how to use chronyd as my local ntp server. On my old servers with ntpd I had local access control lines like: restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap But in looking for documentation on chronyd I did not find anything on this at: https://chrony.tuxfa...

AFAIK the only thing needed to make your host an NTP server using chrony is to set the allow line to the network address in CIDR format of the network you want to be served, and uncomment it. The restart chronyd. You also need to ensure that port 123 (NTP) is open to your internal network on your filrewall. I have a CentOS 6 box that is an NTP server for my network. CentOS 7 works the same way. On 12/27/2016 08:25 AM, Fred Smith wrote: > On Mon, Dec 26, 2016 at 11:04:22PM -0500, Robert Moskowitz w...

Hi, As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd for some reason [3] ? I based my configurations on [1] which use ntpd ... but I thinking change for chronyd , change ntp deamons could outage the samba service and client computers ? Thanks [1] https://negativo17.org/samba-4-active-directory-with-bind-dlz-zones-dynami...

...ing changes to your NTP server, there is the restrict instead of allow command. Its intent is to limit what the server will accept from a host in the address range instead of allowing any command from within that range. I use this on my Centos6 servers. I guess I will have to register to the chronyd list and ask there. thanks On 12/27/2016 08:49 AM, David Both wrote: > AFAIK the only thing needed to make your host an NTP server using > chrony is to set the allow line to the network address in CIDR format > of the network you want to be served, and uncomment it. The restart >...

On 5/24/2015 12:22 PM, Gordon Messmer wrote: > On 05/24/2015 11:41 AM, Kirk Bocek wrote: >> to activate your selected daemon. I just used the new systemd commands, >> thinking that would be enough. So I tried that and rebooted. Nope, same >> problem: > > chronyd and ntpd both use UDP port 123, so each will terminate the > other when it starts. If both are enabled, chronyd's unit file > indicates that it should start after ntpd, so it will always "win." > > You probably have both enabled, so the system boots, starts ntpd, then...

On Mon, Dec 26, 2016 at 11:04:22PM -0500, Robert Moskowitz wrote: > This is for centos 7 that has chronyd 2.1.1 > > I am looking into how to use chronyd as my local ntp server. > > On my old servers with ntpd I had local access control lines like: > > restrict 192.168.128.0 mask 255.255.255.0 nomodify notrap > > > But in looking for documentation on chronyd I did not fin...

Hi All, Just noticed a funny time jump on a testing CentOS 7 VM. Specifically the system time jumps around by a few hours during system boot. The below is a selection from /var/log/messages during boot: Jan 19 12:49:57 arr-data-dev chronyd[716]: Frequency -0.829 +/- 0.007 ppm read from /var/lib/chrony/drift Jan 19 12:49:57 arr-data-dev polkitd[720]: Started polkitd version 0.112 Jan 19 12:49:57 arr-data-dev systemd: Starting D-Bus System Message Bus... Jan 19 12:49:57 arr-data-dev systemd: Starting GSSAPI Proxy Daemon... Jan 19 12:49...

On 5/23/2015 11:22 PM, Luigi Rosa wrote: > Kirk Bocek wrote on 24/05/2015 04:37: >> So I've built my first CentOS 7 host and am learning all the new ways >> of doing >> things. I setup and enabled ntpd but after a reboot I get: > > In CentOS 7 is bettere to use chrony, here's an howto > > http://linoxide.com/linux-command/chrony-time-sync/ > So

Robert, If your NTP server will be on 7/24, I would uninstall chrony and install ntpd which is still included in CentOS 7. Configure as usual. For the differences between chrony and ntpd reference: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ Essentially, chrony is more for laptops with intermittant network connections, and ntpd is better suited to always-on servers

My Centos7 system does not have a battery for the clock (like most armv7 SOCs), thus I rely on that at some point in boot time, chronyd sets the time. If a file is updated prior to chronyd accomplishing its task (or network connectivity is down), the file ends up with a timestamp of "Dec 31 1969". I notice that occasionally, after a reboot, /etc/aliases.db reverts to this time, and I have to run newaliases to fix i...

On Thu, 2019-10-24 at 16:27 +0100, Rowland penny via samba wrote: > On 24/10/2019 16:10, S?rgio Basto via samba wrote: > > Hi, > > As Centos 7 and Fedora defaults to chronyd [2] , should I use ntpd > > for > > some reason [3] ? I based my configurations on [1] which use ntpd > > ... > > but I thinking change for chronyd , change ntp deamons could outage > > the > > samba service and client computers ? > > > There should be...

So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. What other services need to be delayed? Apache? Bind? Of course if this is a nameserver, Chronyd will probably not be able to resolve the NTP server addresses until Bind is running! thanks

Hi, If I run timemaster from systemd it fails with:- Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19231 started: /usr/sbin/chronyd -u chrony -n -f /var/run/timemaster/chrony.conf Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19232 started: /usr/sbin/ptp4l -l 5 -f /var/run/timemaster/ptp4l.0.conf -H -i eno1 Aug 02 06:07:41 machinename timemaster[19230]: [1494069.352] process 19233 started: /usr/sbin/phc2s...

On 05/24/2015 11:41 AM, Kirk Bocek wrote: > to activate your selected daemon. I just used the new systemd commands, > thinking that would be enough. So I tried that and rebooted. Nope, same > problem: chronyd and ntpd both use UDP port 123, so each will terminate the other when it starts. If both are enabled, chronyd's unit file indicates that it should start after ntpd, so it will always "win." You probably have both enabled, so the system boots, starts ntpd, then starts chronyd whic...

...mention, are sure your time sync over AD is working correctly. > One to add to you list, check times of server and clients, (* yes again, > if needed just to be sure). > Yes, I have double check that time is correctly being synced. FYI, Rowland, the process outlined in the wiki for using chronyd does not work on Ubuntu 18.04 (my AD DC is on Ubuntu, but my file server is CentOS). I can only successfully sync windows clients with ntpd running on the DC. Also, if using apparmor, the default apparmor rules don't work. Here's what I had to do to get windows clients to successfully syn...

...for "Time Synchronisation - SELinux Labeling and Policy" on https://wiki.samba.org/index.php/Time_Synchronisation_-_SELinux_Labeling_and_Policy don't seem to work on CentOS 8. Using chrony I tried to adapt them (with very limited SELinux knowledge) like this: chcon -u system_u -t chronyd_exec_t /var/lib/samba/ntp_signd semanage fcontext -a -t chronyd_exec_t "/var/lib/samba/ntp_signd(/.*)?" restorecon -R -v /var/lib/samba/ntp_signd This seems to work on one DC, on the other I'm seeing this in the logs: "platform-python[1654]: SELinux is preventing chronyd from s...

...e been trying out the Restart= option in some of my own systemd service unit files - which appears to work fine However, I notice that this option is only used in a few OS provided service unit files - and was wondering about the wisdom of adding this capability to other daemons/services? (e.g. chronyd or ntpd, crond, rpcbind, etc, etc) - not that these daemons are likely to crash and need restarting that often ... Previously, I've used custom scripts to monitor the state of key daemons and restart or report their status as appropriate - but as systemd has 'Restart' and 'OnFa...

On 04/20/2017 05:16 PM, Warren Young wrote: > On Apr 20, 2017, at 3:00 PM, Robert Moskowitz <rgm at htt-consult.com> wrote: >> So I have learned that Postfix should delay until Chronyd has moved the system time from 0 to current. > I think it?s more the case that CentOS is written with the assumption that you?re running it on a host with a battery-backed RTC, so that system time isn?t wildly off at boot time. This includes VMs, since the VM host should pass its RTC through to...

I have read: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ My server is up all the time and will serve time to internal systems (via DHCP options). Caveat is that my server is an armv7 (Cubieboard2) which does not have an RTC (no battery). So whenever the system boots, the time is ZERO (Dec 31, 1969 or some such). Chrony fixes this really fast; sho...

...mba.org> wrote: > > Does chrony have to be built in some special way to enable ntp-signd? > > Needs to be configured with "--enable-ntp-signd". I may have to build from sources. I downloaded from the SlackBuilds repo and have no idea how it was built. Is there an option to chronyd to list build options? I didn't see one in the manpage. > Also for comparison: > # ls -al /var/lib/samba/ntp_signd/ > total 8 > drwxr-x--- 2 root _chrony 4096 Jan 14 11:14 . > drwxr-xr-x 9 root root 4096 Jan 14 11:14 .. > srwxrwxrwx 1 root root 0 Jan 14 11:14 socket...