gmane.comp.time.chrony.user

4029 articles on record, showing the most recent 50.

Re: Re: NetworkManager dispatcher script(20-chrony) not working on systemd-networkd
Mon, 3 Aug 2026 17:08:37 +0200
Miroslav Lichvar <[email protected]> • #4444
Re: NetworkManager dispatcher script(20-chrony) not working on systemd-networkd
Sat, 25 Jul 2026 15:47:22 +1000
Cooper <[email protected]> • #4443
Re: Frequency of requests to a source whether it is available again
Tue, 21 Jul 2026 12:31:14 +0200
Miroslav Lichvar <[email protected]> • #4442
Frequency of requests to a source whether it is available again
Mon, 20 Jul 2026 15:11:03 +0000
Kaelin Philippe SBB CFF FFS <[email protected]> • #4441
Re: Hardware time stamping and PHY specific features
Mon, 13 Jul 2026 11:39:52 +0200
Pascal Regache <[email protected]> • #4440
Re: Hardware time stamping and PHY specific features
Mon, 13 Jul 2026 10:30:03 +0200
Miroslav Lichvar <[email protected]> • #4439
Hardware time stamping and PHY specific features
Fri, 10 Jul 2026 23:35:28 +0200
Pascal Regache <[email protected]> • #4438
Re: SatPulse: server-oriented alternative to gpsd for chrony
Mon, 11 May 2026 10:06:57 +0200
Miroslav Lichvar <[email protected]> • #4437
Re: SatPulse: server-oriented alternative to gpsd for chrony
Fri, 8 May 2026 09:15:50 +0700
James Clark <[email protected]> • #4436
Re: SatPulse: server-oriented alternative to gpsd for chrony
Thu, 7 May 2026 16:27:18 +0200
Miroslav Lichvar <[email protected]> • #4435
Re: SatPulse: server-oriented alternative to gpsd for chrony
Fri, 24 Apr 2026 10:17:15 +0700
James Clark <[email protected]> • #4434
Re: SatPulse: server-oriented alternative to gpsd for chrony
Thu, 23 Apr 2026 16:09:00 +0200
Miroslav Lichvar <[email protected]> • #4433
Re: SatPulse: server-oriented alternative to gpsd for chrony
Thu, 23 Apr 2026 20:30:27 +0700
James Clark <[email protected]> • #4432
Re: SatPulse: server-oriented alternative to gpsd for chrony
Thu, 23 Apr 2026 12:18:43 +0200
Miroslav Lichvar <[email protected]> • #4431
Re: SatPulse: server-oriented alternative to gpsd for chrony
Thu, 23 Apr 2026 14:46:22 +0700
James Clark <[email protected]> • #4430
Re: SatPulse: server-oriented alternative to gpsd for chrony
Mon, 20 Apr 2026 16:30:22 +0200
Miroslav Lichvar <[email protected]> • #4429
Re: SatPulse: server-oriented alternative to gpsd for chrony
Fri, 17 Apr 2026 19:26:22 +0700
James Clark <[email protected]> • #4428
Re: SatPulse: server-oriented alternative to gpsd for chrony
Tue, 14 Apr 2026 12:58:25 +0200
Miroslav Lichvar <[email protected]> • #4427
Re: SatPulse: server-oriented alternative to gpsd for chrony
Tue, 14 Apr 2026 12:13:11 +0200
James Clark <[email protected]> • #4426
Re: SatPulse: server-oriented alternative to gpsd for chrony
Tue, 14 Apr 2026 09:55:17 +0200
Miroslav Lichvar <[email protected]> • #4425
Re: SatPulse: server-oriented alternative to gpsd for chrony
Tue, 14 Apr 2026 04:42:41 +0200
James Clark <[email protected]> • #4424
Re: SatPulse: server-oriented alternative to gpsd for chrony
Tue, 14 Apr 2026 04:25:07 +0200
James Clark <[email protected]> • #4423
Re: SatPulse: server-oriented alternative to gpsd for chrony
Mon, 13 Apr 2026 10:54:26 +0200
Miroslav Lichvar <[email protected]> • #4422
SatPulse: server-oriented alternative to gpsd for chrony
Sun, 12 Apr 2026 07:08:56 +0200
James Clark <[email protected]> • #4421
Re: Re: chronyd (from chrony-4.3-2+deb12u1) not respond to client NTPv3 request
Mon, 9 Feb 2026 10:59:39 +0100
Miroslav Lichvar <[email protected]> • #4420
Re: chronyd (from chrony-4.3-2+deb12u1) not respond to client NTPv3 request
Sun, 8 Feb 2026 14:22:18 +0100
Franta Hanzlík <franta-8CMi+4rsZoHtwjQa/[email protected]> • #4419
chronyd (from chrony-4.3-2+deb12u1) not respond to client NTPv3 request
Sun, 8 Feb 2026 09:41:17 +0100
Franta Hanzlík <franta-8CMi+4rsZoHtwjQa/[email protected]> • #4418
Re: Guidance on PHC refclock validity/stratum handling in chrony
Thu, 5 Feb 2026 08:13:45 +0100
Miroslav Lichvar <[email protected]> • #4417
Re: Chrony and NTP hardening
Thu, 5 Feb 2026 08:06:18 +0100
Miroslav Lichvar <[email protected]> • #4416
Re: Chrony and NTP hardening (fwd)B
Wed, 4 Feb 2026 09:28:18 -0800 (PST)
Bill Unruh <[email protected]> • #4415
Re: Chrony and NTP hardening
Wed, 4 Feb 2026 18:01:32 +0100
[email protected] • #4414
Re: Chrony and NTP hardening
Wed, 4 Feb 2026 17:50:02 +0100
Bernd Brandstetter <kde-bbrand-CB8Jegt/[email protected]> • #4413
Re: Chrony and NTP hardening
Wed, 4 Feb 2026 17:41:09 +0100
Bernd Brandstetter <kde-bbrand-CB8Jegt/[email protected]> • #4412
Re: Chrony and NTP hardening
Wed, 4 Feb 2026 17:27:04 +0100
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4411
Re: Chrony and NTP hardening
Wed, 4 Feb 2026 17:25:26 +0100
Holger Hoffstätte <[email protected]> • #4410
Chrony and NTP hardening
Wed, 4 Feb 2026 16:57:27 +0100
Bernd Brandstetter <kde-bbrand-CB8Jegt/[email protected]> • #4409
Re: Chrony client on host with server running in LXC on same host
Tue, 03 Feb 2026 20:32:31 +0100
Joachim Tingvold <joachim-5aLZm4DENTRWk0Htik3J/[email protected]> • #4408
Re: Chrony client on host with server running in LXC on same host
Tue, 3 Feb 2026 15:31:29 +0100
Miroslav Lichvar <[email protected]> • #4407
Re: Chrony client on host with server running in LXC on same host
Mon, 2 Feb 2026 12:02:34 +0100
Miroslav Lichvar <[email protected]> • #4406
Chrony client on host with server running in LXC on same host
Sat, 31 Jan 2026 19:23:12 +0100
Joachim Tingvold <joachim-5aLZm4DENTRWk0Htik3J/[email protected]> • #4405
Re: Impact of multiple NTP implementations in containers on host chronyd
Mon, 19 Jan 2026 05:46:09 -0500
"Kevin P. Fleming" <lists.chrony-users-OTXIk8dSW/[email protected]> • #4404
Re: Impact of multiple NTP implementations in containers on host chronyd
Mon, 19 Jan 2026 11:30:53 +0100
Jan Lübbe <[email protected]> • #4403
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Mon, 19 Jan 2026 10:50:56 +0100
Miroslav Lichvar <[email protected]> • #4402
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Fri, 16 Jan 2026 13:16:22 -0800 (PST)
Bill Unruh <[email protected]> • #4401
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Sat, 17 Jan 2026 09:49:06 +1300
Chris Hodgetts <[email protected]> • #4400
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Fri, 16 Jan 2026 12:35:54 -0800 (PST)
Bill Unruh <[email protected]> • #4399
Re: Impact of multiple NTP implementations in containers on host chronyd
Fri, 16 Jan 2026 14:40:55 +0100
Holger Hoffstätte <[email protected]> • #4398
Impact of multiple NTP implementations in containers on host chronyd
Fri, 16 Jan 2026 13:04:24 +0000
"Valera Requena, Juan" <[email protected]> • #4397
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Fri, 16 Jan 2026 21:44:22 +1300
Chris Hodgetts <[email protected]> • #4396
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Thu, 15 Jan 2026 22:56:07 -0800 (PST)
Bill Unruh <[email protected]> • #4395