gmane.comp.time.chrony.user archive

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

Silent Failure -- Enhancement Request
Thu, 18 Apr 2024 22:45:10 +0000
Chris Knox <Christopher.Knox-E0T7EY2UX4gpIyhaTEd/[email protected]> • #4045
Understand why system clock is bad even though chrony offsets look fine
Fri, 19 Apr 2024 02:44:21 +0530
Abhijith Sethuraj <[email protected]> • #4044
Re: Temporarily stop syncing
Wed, 17 Apr 2024 12:39:33 -0400
Jeffrey Kane Johnson <[email protected]> • #4043
Re: Temporarily stop syncing
Wed, 17 Apr 2024 18:30:34 +0200
Miroslav Lichvar <[email protected]> • #4042
Temporarily stop syncing
Wed, 17 Apr 2024 11:40:17 -0400
Jeffrey Kane Johnson <[email protected]> • #4041
Re: Recommendation on chrony with 1pps
Mon, 15 Apr 2024 11:26:01 +0200
Miroslav Lichvar <[email protected]> • #4040
Re: Clarification of terminologies
Mon, 15 Apr 2024 11:19:48 +0200
Miroslav Lichvar <[email protected]> • #4039
Clarification of terminologies
Tue, 9 Apr 2024 17:04:37 +0530
Abhijith Sethuraj <[email protected]> • #4038
Recommendation on chrony with 1pps
Tue, 9 Apr 2024 19:23:25 +0530
Abhijith Sethuraj <[email protected]> • #4037
Clarification of terminologies
Wed, 3 Apr 2024 03:22:27 +0530
Abhijith Sethuraj <[email protected]> • #4036
Re: minstratum directive option
Thu, 21 Mar 2024 15:29:01 +0000
Sviatoslav Feshchenko <[email protected]> • #4035
Re: minstratum directive option
Thu, 21 Mar 2024 16:02:44 +0100
Miroslav Lichvar <[email protected]> • #4034
Re: Re: Using gpsd
Wed, 20 Mar 2024 11:20:49 -0700 (PDT)
Bill Unruh <[email protected]> • #4033
Re: Using gpsd
Wed, 20 Mar 2024 10:29:49 -0700
[email protected] • #4032
Re: minstratum directive option
Wed, 20 Mar 2024 08:07:45 -0700
Denny Page <[email protected]> • #4031
Re: Re: Using gpsd
Tue, 19 Mar 2024 23:48:24 -0700 (PDT)
Bill Unruh <[email protected]> • #4030
Re: Using gpsd
Tue, 19 Mar 2024 21:57:16 -0700
[email protected] • #4029
Re: minstratum directive option
Tue, 19 Mar 2024 19:03:56 -0700 (PDT)
Bill Unruh <[email protected]> • #4028
minstratum directive option
Wed, 20 Mar 2024 01:49:38 +0000
Sviatoslav Feshchenko <[email protected]> • #4027
Re: Using gpsd
Tue, 19 Mar 2024 20:57:00 -0400
David Campbell <[email protected]> • #4026
Re: Using gpsd
Tue, 19 Mar 2024 20:51:15 -0400
David Campbell <[email protected]> • #4025
Re: Using gpsd
Wed, 20 Mar 2024 07:43:20 +0700
James Clark <[email protected]> • #4024
Re: Using gpsd
Tue, 19 Mar 2024 17:29:40 -0700 (PDT)
Bill Unruh <[email protected]> • #4023
Re: Using gpsd
Tue, 19 Mar 2024 19:53:13 -0400
David Campbell <[email protected]> • #4022
Re: Using gpsd
Tue, 19 Mar 2024 14:39:03 -0700 (PDT)
Bill Unruh <[email protected]> • #4021
Using gpsd
Tue, 19 Mar 2024 17:17:45 -0400
David Campbell <[email protected]> • #4020
Re: Perms on refclock socket
Mon, 18 Mar 2024 10:13:31 -0700
[email protected] • #4019
Re[3]: Repeated 'refresh'es may cause excessive DNS queries
Mon, 18 Mar 2024 17:09:17 +0100
[email protected] • #4018
Re: Perms on refclock socket
Mon, 18 Mar 2024 09:15:57 +0100
Miroslav Lichvar <[email protected]> • #4017
Perms on refclock socket
Sun, 17 Mar 2024 16:06:48 -0700
[email protected] • #4016
Antwort: Re: Re: Repeated 'refresh'es may cause excessive DNS queries
Thu, 14 Mar 2024 17:07:25 +0100
[email protected] • #4015
Re: Re: Repeated 'refresh'es may cause excessive DNS queries
Thu, 14 Mar 2024 16:45:49 +0100
Miroslav Lichvar <[email protected]> • #4014
Re: Re: Repeated 'refresh'es may cause excessive DNS queries
Wed, 13 Mar 2024 14:05:06 +0100
Miroslav Lichvar <[email protected]> • #4013
Antwort: Re: Repeated 'refresh'es may cause excessive DNS queries
Wed, 13 Mar 2024 10:11:30 +0100
[email protected] • #4012
Re: Repeated 'refresh'es may cause excessive DNS queries
Tue, 12 Mar 2024 17:14:13 -0500
Matt Rude <matt-5MXZ7I6++7MvAsz/[email protected]> • #4011
Re: Re: Repeated 'refresh'es may cause excessive DNS queries
Tue, 12 Mar 2024 17:35:06 +0100
[email protected] • #4010
Re: Repeated 'refresh'es may cause excessive DNS queries
Tue, 12 Mar 2024 17:02:34 +0100
Miroslav Lichvar <[email protected]> • #4009
Repeated 'refresh'es may cause excessive DNS queries
Tue, 12 Mar 2024 16:35:59 +0100
[email protected] • #4008
Re: Normal? "delay xxx is too high, ignoring" Fix?
Mon, 19 Feb 2024 08:05:57 +0100
Miroslav Lichvar <[email protected]> • #4007
Normal? "delay xxx is too high, ignoring" Fix?
Sun, 18 Feb 2024 16:21:50 +0000
Tovli Toda <[email protected]> • #4006
Re: Per-source address family preference
Fri, 16 Feb 2024 01:03:22 -0500
Rob Foehl <[email protected]> • #4005
Re: Chrony refclock socket 'disappears'
Mon, 12 Feb 2024 08:20:01 -0500
"Kevin P. Fleming" <lists.chrony-users-OTXIk8dSW/[email protected]> • #4004
Re: Chrony refclock socket 'disappears'
Mon, 12 Feb 2024 14:13:08 +0100
Miroslav Lichvar <[email protected]> • #4003
Chrony refclock socket 'disappears'
Mon, 12 Feb 2024 07:14:24 -0500
"Kevin P. Fleming" <lists.chrony-users-OTXIk8dSW/[email protected]> • #4002
Re: Per-source address family preference
Mon, 12 Feb 2024 08:23:57 +0100
Miroslav Lichvar <[email protected]> • #4001
Re: python configuration builder
Tue, 6 Feb 2024 10:01:10 -0800
"Jerry Scharf (he/him)" <[email protected]> • #4000
Re: python configuration builder
Tue, 6 Feb 2024 08:44:07 +0100
Miroslav Lichvar <[email protected]> • #3999
python configuration builder
Mon, 5 Feb 2024 10:40:08 -0800
"Jerry Scharf (he/him)" <[email protected]> • #3998
Re: Fail to sync after eventual internet connection
Mon, 5 Feb 2024 09:28:55 +0100
Miroslav Lichvar <[email protected]> • #3997
Fail to sync after eventual internet connection
Fri, 2 Feb 2024 15:06:12 +0000
Alan Young <[email protected]> • #3996
Re: SV: SV: Output from chronyc sources -v
Thu, 25 Jan 2024 14:38:06 +0100
Miroslav Lichvar <[email protected]> • #3995
SV: SV: Output from chronyc sources -v
Thu, 25 Jan 2024 13:19:41 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #3994
Re: SV: Output from chronyc sources -v
Wed, 24 Jan 2024 14:30:11 +0100
Miroslav Lichvar <[email protected]> • #3993
SV: Output from chronyc sources -v
Wed, 24 Jan 2024 12:25:27 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #3992
Re: Output from chronyc sources -v
Wed, 24 Jan 2024 09:31:18 +0100
Miroslav Lichvar <[email protected]> • #3991
Output from chronyc sources -v
Wed, 24 Jan 2024 00:37:03 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #3990
Re: No packets transmitted when using Yocto 4.3.1
Tue, 16 Jan 2024 15:38:37 +0100
Miroslav Lichvar <[email protected]> • #3989
Re: No packets transmitted when using Yocto 4.3.1
Tue, 16 Jan 2024 15:09:23 +0100
Thomas Lange <[email protected]> • #3988
confirm unsubscribe e748c16eb2b52284a170835a1f48ab07
Mon, 15 Jan 2024 17:06:10 +0000
"Whelan, Andy" <awhelan-s5OS3+GPyY/[email protected]> • #3987
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 15:14:05 +0100
Miroslav Lichvar <[email protected]> • #3986
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 20:56:41 +0700
James Clark <[email protected]> • #3985
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 14:15:09 +0100
Miroslav Lichvar <[email protected]> • #3984
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 18:57:48 +0700
James Clark <[email protected]> • #3983
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 12:32:39 +0100
Miroslav Lichvar <[email protected]> • #3982
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 18:09:53 +0700
James Clark <[email protected]> • #3981
Re: Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 10:27:32 +0100
Miroslav Lichvar <[email protected]> • #3980
Nanosecond precision with refclock SOCK
Mon, 15 Jan 2024 13:05:32 +0700
James Clark <[email protected]> • #3979
Re: No packets transmitted when using Yocto 4.3.1
Sun, 7 Jan 2024 11:08:47 +0100
Thomas Lange <[email protected]> • #3978
Re: No packets transmitted when using Yocto 4.3.1
Fri, 5 Jan 2024 10:56:02 +0100
Thomas Lange <[email protected]> • #3977
Re: 答复 : ntptime returned error 5
Wed, 3 Jan 2024 11:09:31 +0100
Miroslav Lichvar <[email protected]> • #3976
答复: [chrony-users] ntptime returned error 5
Wed, 3 Jan 2024 07:51:13 +0000
chengyechun <[email protected]> • #3975
答复: [chrony-users] ntptime returned error 5
Wed, 3 Jan 2024 07:48:46 +0000
chengyechun <[email protected]> • #3974
Re: ntptime returned error 5
Wed, 3 Jan 2024 08:44:30 +0100
Miroslav Lichvar <[email protected]> • #3973
Re: ntptime returned error 5
Tue, 2 Jan 2024 21:23:33 -0800 (PST)
Bill Unruh <[email protected]> • #3972
ntptime returned error 5
Wed, 3 Jan 2024 02:09:31 +0000
chengyechun <[email protected]> • #3971
Re: Re: Re: No packets transmitted when using Yocto 4.3.1
Wed, 3 Jan 2024 00:33:06 +0100
Thomas Lange <[email protected]> • #3970
Re: Re: No packets transmitted when using Yocto 4.3.1
Tue, 2 Jan 2024 09:17:25 -0800
[email protected] • #3969
Re: No packets transmitted when using Yocto 4.3.1
Tue, 2 Jan 2024 12:36:12 +0100
Miroslav Lichvar <[email protected]> • #3968
Re: No packets transmitted when using Yocto 4.3.1
Tue, 2 Jan 2024 11:54:32 +0100
Thomas Lange <[email protected]> • #3967
Re: No packets transmitted when using Yocto 4.3.1
Tue, 2 Jan 2024 11:34:11 +0100
Miroslav Lichvar <[email protected]> • #3966
No packets transmitted when using Yocto 4.3.1
Fri, 15 Dec 2023 11:46:57 +0100
Thomas Lange <[email protected]> • #3965
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 20:46:45 +0200
Avamander <[email protected]> • #3964
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 19:27:03 +0100
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #3963
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 19:19:25 +0100
Adrian Zaugg <[email protected]> • #3962
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 09:45:17 -0800 (PST)
Bill Unruh <[email protected]> • #3961
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 09:10:08 -0800
Ian Zimmerman <[email protected]> • #3960
Re: DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 17:57:20 +0100
Miroslav Lichvar <[email protected]> • #3959
Re: Improvement request: network status should not affect chronyc
Tue, 12 Dec 2023 08:34:29 -0800 (PST)
Bill Unruh <[email protected]> • #3958
DNS/DKIM issue with tuxfamily.org?
Tue, 12 Dec 2023 13:50:17 +0000
Joe Smith <[email protected]> • #3957
RE: Improvement request: network status should not affect chronyc
Tue, 12 Dec 2023 12:22:05 +0000
"Hollerer Franz, Schrack Seconet AG, Entwicklung" <[email protected]> • #3956
Re: Improvement request: network status should not affect chronyc
Tue, 12 Dec 2023 07:10:11 -0500
"Kevin P. Fleming" <lists.chrony-users-OTXIk8dSW/[email protected]> • #3955
Improvement request: network status should not affect chronyc
Tue, 12 Dec 2023 12:07:20 +0000
"Hollerer Franz, Schrack Seconet AG, Entwicklung" <[email protected]> • #3954
Re: How to Delay Chrony Start Until After PPS Device Attached
Mon, 11 Dec 2023 15:17:27 +0100
Miroslav Lichvar <[email protected]> • #3953
Re: How to Delay Chrony Start Until After PPS Device Attached
Sat, 9 Dec 2023 09:39:33 -0800 (PST)
Bill Unruh <[email protected]> • #3952
Re: How to Delay Chrony Start Until After PPS Device Attached
Sat, 09 Dec 2023 06:16:11 -0500
"Kevin P. Fleming" <lists.chrony-users-OTXIk8dSW/[email protected]> • #3951
How to Delay Chrony Start Until After PPS Device Attached
Fri, 8 Dec 2023 21:59:32 -0500
Joshua Quesenberry <[email protected]> • #3950
Re: Trouble running chronyd on old hardware
Thu, 7 Dec 2023 10:20:59 +0800
Ahmed Habub <[email protected]> • #3949
chrony-4.5 released
Tue, 5 Dec 2023 15:17:40 +0100
Miroslav Lichvar <[email protected]> • #3948
Re: Trouble running chronyd on old hardware
Mon, 4 Dec 2023 08:19:10 -0800 (PST)
Bill Unruh <[email protected]> • #3947
Re: Trouble running chronyd on old hardware
Mon, 4 Dec 2023 16:37:16 +0100
Miroslav Lichvar <[email protected]> • #3946
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.