gmane.comp.time.chrony.user archive

603 archived articles, newest first (page 1 of 7). Latest articles →

chrony-4.9-pre1 released
Wed, 12 Aug 2026 16:17:39 +0200
Miroslav Lichvar <[email protected]> • #4445
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
Re: System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Fri, 16 Jan 2026 19:35:09 +1300
Chris Hodgetts <[email protected]> • #4394
System Clock is updated before the TAI-UTC offset is applied for PHC source in chrony 6.4.1
Fri, 16 Jan 2026 06:28:35 +0000
Simon Plackett <[email protected]> • #4393
Re: Questions about "holdover" state
Mon, 12 Jan 2026 16:57:42 +0100
Miroslav Lichvar <[email protected]> • #4392
Questions about "holdover" state
Mon, 12 Jan 2026 11:29:24 +0000
"Valera Requena, Juan" <[email protected]> • #4391
Re: Question about adding custom serial time source with PPS to chrony
Thu, 27 Nov 2025 09:00:20 +0100
Miroslav Lichvar <[email protected]> • #4390
Question about adding custom serial time source with PPS to chrony
Thu, 27 Nov 2025 07:16:22 +0100
Awais Muhammad <[email protected]> • #4389
Re: PTP TAI Query
Tue, 25 Nov 2025 01:37:13 +1300
Chris Hodgetts <[email protected]> • #4388
Re: PTP TAI Query
Mon, 24 Nov 2025 09:39:19 +0100
Miroslav Lichvar <[email protected]> • #4387
PTP TAI Query
Sun, 23 Nov 2025 21:23:05 +1300
Chris Hodgetts <[email protected]> • #4386
Re: chronyc serverstats => 501 not autorized
Thu, 20 Nov 2025 18:38:10 +0100
Gerd Hoerst <[email protected]> • #4385
Re: chronyc serverstats => 501 not autorized
Thu, 20 Nov 2025 09:10:38 +0100 (GMT+01:00)
Gerd Hoerst <[email protected]> • #4384
Re: chronyc serverstats => 501 not autorized
Thu, 20 Nov 2025 08:28:35 +0100
Miroslav Lichvar <[email protected]> • #4383
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 17:21:55 +0100
Gerd Hoerst <[email protected]> • #4382
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 15:58:16 +0100
Gerd Hoerst <[email protected]> • #4381
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 15:54:02 +0100
Miroslav Lichvar <[email protected]> • #4380
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 15:37:23 +0100
Gerd Hoerst <[email protected]> • #4379
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 15:34:30 +0100
Gerd Hoerst <[email protected]> • #4378
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 13:44:43 +0100
Miroslav Lichvar <[email protected]> • #4377
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 13:38:18 +0100
Gerd Hoerst <[email protected]> • #4376
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 09:59:10 +0100
Miroslav Lichvar <[email protected]> • #4375
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 09:45:39 +0100
Gerd Hoerst <[email protected]> • #4374
Re: chronyc serverstats => 501 not autorized
Wed, 19 Nov 2025 08:22:58 +0100
Miroslav Lichvar <[email protected]> • #4373
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 16:49:00 +0100 (GMT+01:00)
Gerd Hoerst <[email protected]> • #4372
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 16:08:16 +0100
Miroslav Lichvar <[email protected]> • #4371
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 15:04:11 +0100
Gerd Hoerst <[email protected]> • #4370
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 14:49:31 +0100
Miroslav Lichvar <[email protected]> • #4369
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 14:44:17 +0100
Gerd Hoerst <[email protected]> • #4368
Re: chronyc serverstats => 501 not autorized
Tue, 18 Nov 2025 08:37:05 +0100
Miroslav Lichvar <[email protected]> • #4367
chronyc serverstats => 501 not autorized
Fri, 14 Nov 2025 12:41:09 +0100
Gerd Hoerst <[email protected]> • #4366
RE: [Question] chronyc tracking shows large offset
Wed, 5 Nov 2025 10:28:58 +0000
MUZZULINI Frank <[email protected]> • #4365
Re: [Question] chronyc tracking shows large offset
Wed, 5 Nov 2025 01:28:15 -0800 (PST)
Bill Unruh <[email protected]> • #4364
Re: [Question] chronyc tracking shows large offset
Wed, 5 Nov 2025 10:18:50 +0100
Miroslav Lichvar <[email protected]> • #4363
[Question] chronyc tracking shows large offset
Wed, 5 Nov 2025 17:07:32 +0800
zc z <[email protected]> • #4362
[Question] chronyc tracking shows large offset
Wed, 5 Nov 2025 16:41:06 +0800
zc z <[email protected]> • #4361
Re: Chronyd NTS under Ubuntu 24 - group permissions
Tue, 16 Sep 2025 08:27:08 +0200
Christian Ehrhardt <[email protected]> • #4360
Chronyd NTS under Ubuntu 24 - group permissions
Tue, 16 Sep 2025 02:03:31 +0200
"Mikhail" <mikhail-rh3qjuY/[email protected]> • #4359
Re: FreeBSD socket.test FAIL: recvmsg() error EAGAIN on accept TCP socket receive
Sat, 6 Sep 2025 16:34:41 +0200
Matthias Andree <[email protected]> • #4358
Re: How to disable rate limiting
Mon, 1 Sep 2025 16:12:27 +0200
kross-WHuJl200arIRAJMLapdhQVaTQe2KTcn/@public.gmane.org • #4357
Re: How to disable rate limiting
Mon, 01 Sep 2025 08:49:32 +0200
Jiří Činčura <[email protected]> • #4356
Re: How to disable rate limiting
Mon, 1 Sep 2025 08:35:07 +0200
Miroslav Lichvar <[email protected]> • #4355
Re: How to disable rate limiting
Fri, 29 Aug 2025 14:53:52 +0200
Jiří Činčura <[email protected]> • #4354
How to disable rate limiting
Fri, 29 Aug 2025 14:37:29 +0200 (GMT+02:00)
kross-WHuJl200arIRAJMLapdhQVaTQe2KTcn/@public.gmane.org • #4353
How to disable rate limiting
Fri, 29 Aug 2025 13:31:21 +0200
Jiří Činčura <[email protected]> • #4352
Re: FreeBSD socket.test FAIL: recvmsg() error EAGAIN on accept TCP socket receive
Thu, 28 Aug 2025 10:07:31 +0200
Miroslav Lichvar <[email protected]> • #4351
FreeBSD socket.test FAIL: recvmsg() error EAGAIN on accept TCP socket receive
Wed, 27 Aug 2025 16:50:36 +0200
Matthias Andree <[email protected]> • #4350
chrony-4.8 released
Wed, 27 Aug 2025 14:43:58 +0200
Miroslav Lichvar <[email protected]> • #4349
Re[2]: Occasional large offsets with GPS signal
Thu, 21 Aug 2025 16:07:40 +0000
"Torsten Wolf" <[email protected]> • #4348
Re: Occasional large offsets with GPS signal
Thu, 21 Aug 2025 17:45:49 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4347
Occasional large offsets with GPS signal
Thu, 21 Aug 2025 14:31:42 +0000
"Torsten Wolf" <[email protected]> • #4346
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.