similar to: Chrony vd NTP

On 05/02/17 16:15, Richard wrote: > >> Date: Sunday, February 05, 2017 10:26:05 -0500 >> From: Robert Moskowitz <rgm at htt-consult.com> >> >> I have read: >> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >> ween-ntpd-and-chronyd/ >> >> My server is up all the time and will serve time to internal >> systems (via

> Date: Sunday, February 05, 2017 10:26:05 -0500 > From: Robert Moskowitz <rgm at htt-consult.com> > > I have read: > http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet > ween-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

On 02/05/2017 11:58 AM, J Martin Rushton wrote: > On 05/02/17 16:15, Richard wrote: >>> Date: Sunday, February 05, 2017 10:26:05 -0500 >>> From: Robert Moskowitz <rgm at htt-consult.com> >>> >>> I have read: >>> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >>> ween-ntpd-and-chronyd/ >>> >>> My

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

Hi, the instructions 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

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

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.tuxfamily.org/doc/2.1/manual.html In the actual /etc/chronyd.conf

On 19.01.2025 17:30, Sonic via samba wrote: > When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back in > December of 2023 Chrony was working just fine for a natural domain time > sync to the DC - no special config or GPO necessary. So after seeing this > thread I decided to see what was different about my configuration that > allowed it to work so seamlessly and I was

On Sun, 19 Jan 2025 17:51:54 +0100 Peter Milesson via samba <samba at lists.samba.org> wrote: > > > > On 19.01.2025 17:30, Sonic via samba wrote: > > When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back > > in December of 2023 Chrony was working just fine for a natural > > domain time sync to the DC - no special config or GPO necessary. So >

Hallo, what is the standard way to sync time under Centos 7. ntp or chrony. Thanks for a short hint. Ralf

Op 20-01-2025 om 11:52 schreef Rowland Penny via samba: > On Sun, 19 Jan 2025 17:51:54 +0100 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> >> >> On 19.01.2025 17:30, Sonic via samba wrote: >>> When I first did a Samba upgrade to 4.19.3 on Debian Bookworm back >>> in December of 2023 Chrony was working just fine for a natural

On Sunday, 3 June 2018 16:32:12 CEST Rowland Penny via samba wrote: > On Sun, 3 Jun 2018 17:11:47 +0300 > > Alexei Rozenvaser <alexei.roz at gmail.com> wrote: > > On Sun, Jun 3, 2018 at 4:51 PM Rowland Penny via samba > > > > <samba at lists.samba.org> wrote: > > > On Sun, 3 Jun 2018 16:29:04 +0300 > > > > > > Alexei Rozenvaser

My tests: -Boot a backed up ?new? VM with chrony 4.3 and samba 4.19 installed, joined a new Win 10 machine, time syncs OK with Type: NT5DS. -Updated DC samba to 4.21.3 without removing the Windows machine from domain. Time syncs OK with NT5DS. -Leave domain, try to w32tm /monitor -> error can?t reach DCs (expected) -Join domain again: time syncs OK with NT5DS. I can?t reproduce. Can we make

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,

On Mon, 20 Jan 2025 09:38:50 -0500 Jeffrey Walton via samba <samba at lists.samba.org> wrote: > On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba > <samba at lists.samba.org> wrote: > > > > I noticed a problem with time synchronization on all Windows > > endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. > > > > When I run the following command

On 20 January 2025 15:18 Luis Peromarta wrote: > > I hope to be able to do the same kind of tests, > On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > > Windows 11 Pro (24H2). All those clients report CMOS clock as time > > source. I also suspect that

On 20 January 2025 19:31 Luis Peromarta wrote: > > My tests: > > -Boot a backed up ?new? VM with chrony 4.3 and samba 4.19 installed, joined a new > Win 10 machine, time syncs OK with Type: NT5DS. > -Updated DC samba to 4.21.3 without removing the Windows machine from domain. > Time syncs OK with NT5DS. > -Leave domain, try to w32tm /monitor -> error can?t reach DCs

I noticed a problem with time synchronization on all Windows endpoints. I am using Samba 4.21.3 and Chrony 4.3-2. When I run the following command in Windows: w32tm /monitor dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: ICMP: 1ms delay NTP: +0.0000000s offset from dc1.xxxx.pl RefID: time.cloudflare.com [162.159.200.123] Stratum: 4 dc2.xxxx.pl[192.168.45.9:123]: ICMP: 1ms delay NTP: -0.0001207s

On Sat, Jan 18, 2025 at 3:49?AM Programnet via samba <samba at lists.samba.org> wrote: > > I noticed a problem with time synchronization on all Windows endpoints. > I am using Samba 4.21.3 and Chrony 4.3-2. > > When I run the following command in Windows: > > w32tm /monitor > dc1.xxxx.pl *** PDC ***[192.168.45.10:123]: > ICMP: 1ms delay > NTP: +0.0000000s offset

I hope to be able to do the same kind of tests, On 20 Jan 2025 at 15:10 +0000, Peter Milesson <miles at atmos.eu>, wrote: > > I have tested with Windows 7 Pro (SP1), Windows 10 Pro (22H2), and > Windows 11 Pro (24H2). All those clients report CMOS clock as time > source. I also suspect that something broke in Samba since I posted > about this problem on 9 August 2023. Then I