gmane.comp.time.chrony.user archive

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

Re: Using radio time signal for syncronization
Wed, 8 Jan 2025 09:21:55 +0100
Miroslav Lichvar <[email protected]> • #4245
Re: Using radio time signal for syncronization
Tue, 07 Jan 2025 14:49:52 +0000
Sviatoslav Feshchenko <[email protected]> • #4244
Re: Using radio time signal for syncronization
Tue, 7 Jan 2025 14:28:03 +0100
Gerd Hoerst <[email protected]> • #4243
Re: Using radio time signal for syncronization
Tue, 7 Jan 2025 10:33:50 +0100
Miroslav Lichvar <[email protected]> • #4242
Re: Sources marked as falseticker which shouldn't be
Tue, 7 Jan 2025 17:33:05 +0800
Yuezhen LUAN <[email protected]> • #4241
Re: Sources marked as falseticker which shouldn't be
Tue, 7 Jan 2025 10:09:53 +0100
Miroslav Lichvar <[email protected]> • #4240
Sources marked as falseticker which shouldn't be
Mon, 6 Jan 2025 18:12:53 +0800
Yuezhen LUAN <[email protected]> • #4239
Using radio time signal for syncronization
Sun, 05 Jan 2025 01:22:08 +0000
Sviatoslav Feshchenko <[email protected]> • #4238
Re: chrony gpsd / pps raspberriy Pi4
Thu, 2 Jan 2025 18:15:25 +0100
Gerd Hoerst <[email protected]> • #4237
Re: chrony gpsd / pps raspberriy Pi4
Thu, 2 Jan 2025 13:08:16 +0100
Miroslav Lichvar <[email protected]> • #4236
Re: Periodic time saving to disc (no RTC)
Thu, 2 Jan 2025 13:00:56 +0100
Miroslav Lichvar <[email protected]> • #4235
chrony gpsd / pps raspberriy Pi4
Sun, 22 Dec 2024 22:42:34 +0100
Gerd Hoerst <[email protected]> • #4234
Periodic time saving to disc (no RTC)
Thu, 12 Dec 2024 16:59:08 +0100
Ariel Garcia <[email protected]> • #4233
Re: Disable GPS sync on skew
Tue, 19 Nov 2024 08:52:54 -0500
Shawn Beard <[email protected]> • #4232
Re: Disable GPS sync on skew
Tue, 19 Nov 2024 14:46:36 +0100
Miroslav Lichvar <[email protected]> • #4231
Disable GPS sync on skew
Tue, 19 Nov 2024 08:37:30 -0500
Shawn Beard <[email protected]> • #4230
Re: chronyd -q fails
Mon, 18 Nov 2024 11:44:51 +0100
Miroslav Lichvar <[email protected]> • #4229
chronyd -q fails
Fri, 15 Nov 2024 12:31:32 -0600
Dennis Nelson <[email protected]> • #4228
unsuscribe
Sun, 27 Oct 2024 14:45:09 +0000
2W0YVY <[email protected]> • #4227
confirm unsubscribe e68c898207bba85644ad0006482b12ea
Sat, 26 Oct 2024 17:22:48 -0600
Bill Cody <[email protected]> • #4226
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Sat, 26 Oct 2024 15:20:24 -0700 (PDT)
Bill Unruh <[email protected]> • #4225
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Sat, 26 Oct 2024 21:33:21 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4224
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Fri, 25 Oct 2024 18:13:23 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4223
Re: Multiple Clock Sources Cannot Be Synchronized
Fri, 25 Oct 2024 12:55:31 +0800
egg car <[email protected]> • #4222
答复: [chrony-users] Multiple Clock Sources C annot Be Synchronized
Fri, 25 Oct 2024 03:16:55 +0000
chengyechun <[email protected]> • #4221
答复: [chrony-users] Multiple Clock Sources C annot Be Synchronized
Fri, 25 Oct 2024 01:14:31 +0000
chengyechun <[email protected]> • #4220
Re: Multiple Clock Sources Cannot Be Synchronized
Thu, 24 Oct 2024 15:28:37 +0200
Miroslav Lichvar <[email protected]> • #4219
Multiple Clock Sources Cannot Be Synchronized
Thu, 24 Oct 2024 13:02:40 +0000
chengyechun <[email protected]> • #4218
RE: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Wed, 23 Oct 2024 10:44:53 -0700
<[email protected]> • #4217
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Wed, 23 Oct 2024 10:05:03 -0500
Steven Sommars <[email protected]> • #4216
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Wed, 23 Oct 2024 08:53:43 +0200
Miroslav Lichvar <[email protected]> • #4215
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Wed, 23 Oct 2024 02:02:52 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4214
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Wed, 23 Oct 2024 01:58:56 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4213
Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Tue, 22 Oct 2024 08:44:51 -0700
[email protected] • #4212
Re: Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Tue, 22 Oct 2024 09:28:54 +0200
Miroslav Lichvar <[email protected]> • #4211
Re: Any nice example of chrony, WWVB, Raspberry Pi ?
Mon, 21 Oct 2024 19:14:23 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4210
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 19:58:44 +0200
Nathan MALO <[email protected]> • #4209
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 13:55:50 +0200
Miroslav Lichvar <[email protected]> • #4208
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 12:57:48 +0200
Nathan MALO <[email protected]> • #4207
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 12:49:40 +0200
Miroslav Lichvar <[email protected]> • #4206
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 12:32:25 +0200
Nathan MALO <[email protected]> • #4205
Re: Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 12:23:45 +0200
Miroslav Lichvar <[email protected]> • #4204
Chrony launched with -x in Kubernetes
Mon, 21 Oct 2024 11:42:04 +0200
Nathan MALO <[email protected]> • #4203
Any nice example of chrony, WWVB, Raspberry Pi ?
Tue, 15 Oct 2024 03:26:52 +0000 (UTC)
Mike Collins <mocallins-/[email protected]> • #4202
chrony-4.6.1 released
Tue, 8 Oct 2024 15:34:41 +0200
Miroslav Lichvar <[email protected]> • #4201
Re: (SCAP-Finding) command port has to be closed
Wed, 25 Sep 2024 13:39:09 +0200
Nuß Bratling <[email protected]> • #4200
RE: Is it possible to smooth out jitter caused by USB interface?
Fri, 20 Sep 2024 17:22:30 -0400
"Daniel Gearty" <dpgearty-A7wQCf4NAVlWk0Htik3J/[email protected]> • #4199
Re: Is it possible to smooth out jitter caused by USB interface?
Fri, 20 Sep 2024 13:24:27 -0700 (PDT)
Bill Unruh <[email protected]> • #4198
Is it possible to smooth out jitter caused by USB interface?
Fri, 20 Sep 2024 19:12:42 +0000
Sviatoslav Feshchenko <[email protected]> • #4197
Re: What does the reference time really mean?
Mon, 16 Sep 2024 11:55:13 +0200
Miroslav Lichvar <[email protected]> • #4196
What does the reference time really mean?
Sun, 15 Sep 2024 22:04:17 +0200
Stefan Mayr <stefan-cySBxigrC/[email protected]> • #4195
Re: Integrating SOCK and PPS refclocks using custom application
Thu, 12 Sep 2024 09:55:17 +0200
Miroslav Lichvar <[email protected]> • #4194
Integrating SOCK and PPS refclocks using custom application
Wed, 11 Sep 2024 20:48:16 -0700
Stephen Oneto <[email protected]> • #4193
Re: Fwd: ntp symmetric auth for internal clients
Tue, 3 Sep 2024 09:44:34 +0200
Ede Wolf <listac-WJzqqJJEo14F5JlS/[email protected]> • #4192
chrony-4.6 released
Mon, 2 Sep 2024 15:09:34 +0200
Miroslav Lichvar <[email protected]> • #4191
Re: Fwd: ntp symmetric auth for internal clients
Mon, 2 Sep 2024 14:41:56 +0200
Miroslav Lichvar <[email protected]> • #4190
Fwd: ntp symmetric auth for internal clients
Mon, 2 Sep 2024 14:31:03 +0200
Ede Wolf <listac-WJzqqJJEo14F5JlS/[email protected]> • #4189
Re: ntp symmetric auth for internal clients
Mon, 2 Sep 2024 13:06:18 +0200
Miroslav Lichvar <[email protected]> • #4188
ntp symmetric auth for internal clients
Mon, 2 Sep 2024 12:48:42 +0200
Ede Wolf <listac-WJzqqJJEo14F5JlS/[email protected]> • #4187
RE: (SCAP-Finding) command port has to be closed
Mon, 2 Sep 2024 06:52:08 +0000
MUZZULINI Frank <[email protected]> • #4186
Re: (SCAP-Finding) command port has to be closed
Fri, 23 Aug 2024 18:15:33 +0800
Ahmed Habub <[email protected]> • #4185
Re: (SCAP-Finding) command port has to be closed
Fri, 23 Aug 2024 12:08:47 +0200
Nuß Bratling <[email protected]> • #4184
Re: (SCAP-Finding) command port has to be closed
Thu, 22 Aug 2024 14:40:16 +0200
Miroslav Lichvar <[email protected]> • #4183
(SCAP-Finding) command port has to be closed
Wed, 21 Aug 2024 13:53:13 +0200
Nuß Bratling <[email protected]> • #4182
Re: Recommendation for chrony with 1PPS setup
Wed, 21 Aug 2024 16:52:41 +0530
Abhijith Sethuraj <[email protected]> • #4181
Re: Recommendation for chrony with 1PPS setup
Wed, 21 Aug 2024 08:12:58 +0200
Miroslav Lichvar <[email protected]> • #4180
Re: Recommendation for chrony with 1PPS setup
Tue, 20 Aug 2024 15:06:40 -0700 (PDT)
Bill Unruh <[email protected]> • #4179
Re: Recommendation for chrony with 1PPS setup
Wed, 21 Aug 2024 03:18:43 +0530
Abhijith Sethuraj <[email protected]> • #4178
Re: Recommendation for chrony with 1PPS setup
Wed, 21 Aug 2024 03:13:56 +0530
Abhijith Sethuraj <[email protected]> • #4177
Re: Recommendation for chrony with 1PPS setup
Tue, 20 Aug 2024 12:15:17 +0200
Miroslav Lichvar <[email protected]> • #4176
Recommendation for chrony with 1PPS setup
Tue, 20 Aug 2024 15:23:03 +0530
Abhijith Sethuraj <[email protected]> • #4175
Re:
Mon, 12 Aug 2024 20:35:20 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4174
Re:
Mon, 12 Aug 2024 10:17:17 -0700 (PDT)
Bill Unruh <[email protected]> • #4173
Re: confirm unsubscribe cd0932a36f0086f8f55ddd04731f3c20
Mon, 12 Aug 2024 18:38:40 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4172
Re: confirm unsubscribe cd0932a36f0086f8f55ddd04731f3c20
Mon, 12 Aug 2024 13:59:25 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4171
Re: confirm unsubscribe cd0932a36f0086f8f55ddd04731f3c20
Mon, 12 Aug 2024 13:53:18 +0200
Miroslav Lichvar <[email protected]> • #4170
confirm unsubscribe cd0932a36f0086f8f55ddd04731f3c20
Mon, 12 Aug 2024 11:27:31 +0000
"Whelan, Andy" <awhelan-s5OS3+GPyY/[email protected]> • #4169
Re: How to read the RTC value?
Mon, 12 Aug 2024 10:01:26 +0200
Miroslav Lichvar <[email protected]> • #4168
confirm unsubscribe 865e0486c51bd1940ed3f458314620b0
Mon, 12 Aug 2024 01:03:00 +0000
邹林志08963 <[email protected]> • #4167
Re: How to read the RTC value?
Sat, 10 Aug 2024 07:04:45 -0700 (PDT)
Bill Unruh <[email protected]> • #4166
Re: How to read the RTC value?
Sat, 10 Aug 2024 10:20:06 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4165
Re: Simple DHCP support
Sat, 10 Aug 2024 10:16:45 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4164
Re: Simple DHCP support for chrony
Fri, 9 Aug 2024 18:34:03 -0400
Paul <chrony-users-sq1Vm0FqdD/[email protected]> • #4163
Re: Simple DHCP support
Fri, 9 Aug 2024 15:20:09 -0700
Denny Page <[email protected]> • #4162
Re: Simple DHCP support
Fri, 9 Aug 2024 23:16:19 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4161
Re: Simple DHCP support
Fri, 9 Aug 2024 13:55:24 -0700 (PDT)
Bill Unruh <[email protected]> • #4160
confirm unsubscribe 90111f062b9b5f6b7ad4e70d6
Fri, 9 Aug 2024 20:18:15 +0000
"Whelan, Andy" <awhelan-s5OS3+GPyY/[email protected]> • #4159
Re: Simple DHCP support
Fri, 9 Aug 2024 23:10:45 +0300
Andrei Borzenkov <[email protected]> • #4158
Re: Simple DHCP support
Fri, 9 Aug 2024 13:05:13 -0700 (PDT)
Bill Unruh <[email protected]> • #4157
Re: Simple DHCP support
Fri, 9 Aug 2024 12:50:02 -0700 (PDT)
Bill Unruh <[email protected]> • #4156
Re: How to read the RTC value?
Fri, 9 Aug 2024 12:36:48 -0700 (PDT)
Bill Unruh <[email protected]> • #4155
Re: Simple DHCP support
Fri, 9 Aug 2024 21:28:13 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4154
Re: How to read the RTC value?
Fri, 9 Aug 2024 21:19:55 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4153
Re: Simple DHCP support
Fri, 9 Aug 2024 21:11:00 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4152
Re: How to read the RTC value?
Fri, 9 Aug 2024 21:07:39 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4151
Re: Simple DHCP support
Fri, 9 Aug 2024 20:37:26 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4150
Re: Simple DHCP support for chrony
Fri, 9 Aug 2024 20:35:00 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4149
Re: Simple DHCP support
Fri, 9 Aug 2024 11:33:57 -0700 (PDT)
Bill Unruh <[email protected]> • #4148
Re: Simple DHCP support for chrony
Fri, 9 Aug 2024 20:33:55 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4147
Re: How to read the RTC value?
Fri, 9 Aug 2024 11:25:07 -0700 (PDT)
Bill Unruh <[email protected]> • #4146
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.