gmane.comp.time.chrony.user archive

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

Re: Simple DHCP support for chrony
Fri, 9 Aug 2024 10:09:47 -0700 (PDT)
Bill Unruh <[email protected]> • #4145
Re: How to read the RTC value?
Fri, 9 Aug 2024 17:11:38 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4144
Re: How to read the RTC value?
Fri, 9 Aug 2024 17:10:44 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4143
Simple DHCP support for chrony
Fri, 9 Aug 2024 16:18:13 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4142
Simple DHCP support
Fri, 9 Aug 2024 16:16:35 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4141
How to read the RTC value?
Fri, 9 Aug 2024 16:14:24 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4140
Re: Using cellular network clock as refclock in chrony
Wed, 31 Jul 2024 14:58:09 +0200
Miroslav Lichvar <[email protected]> • #4139
Re: Using cellular network clock as refclock in chrony
Wed, 31 Jul 2024 09:47:05 +0000
Amol Lad <[email protected]> • #4138
Re: Using cellular network clock as refclock in chrony
Wed, 31 Jul 2024 10:52:08 +0200
Miroslav Lichvar <[email protected]> • #4137
Re: Using cellular network clock as refclock in chrony
Wed, 31 Jul 2024 08:42:52 +0000
Amol Lad <[email protected]> • #4136
chrony-4.6-pre1 released
Tue, 30 Jul 2024 14:49:10 +0200
Miroslav Lichvar <[email protected]> • #4135
Re: Using cellular network clock as refclock in chrony
Tue, 30 Jul 2024 14:16:27 +0200
Miroslav Lichvar <[email protected]> • #4134
Using cellular network clock as refclock in chrony
Tue, 30 Jul 2024 12:05:29 +0000
Amol Lad <[email protected]> • #4133
Re: Certain NTS servers not synching, how to best troubleshoot ?
Tue, 30 Jul 2024 08:34:30 +0200
Miroslav Lichvar <[email protected]> • #4132
Re: SV: Certain NTS servers not synching, how to best troubleshoot ?
Tue, 30 Jul 2024 06:24:07 +0000
Laura Smith <n5d9xq3ti233xiyif2vp-g/[email protected]> • #4131
SV: Certain NTS servers not synching, how to best troubleshoot ?
Mon, 29 Jul 2024 22:55:50 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #4130
Certain NTS servers not synching, how to best troubleshoot ?
Mon, 29 Jul 2024 20:27:41 +0000
Laura Smith <n5d9xq3ti233xiyif2vp-g/[email protected]> • #4129
Re: Best strategy for calculating average synchronization time.
Tue, 23 Jul 2024 10:50:35 +0200
Miroslav Lichvar <[email protected]> • #4128
RE: Best strategy for calculating average synchronization time.
Mon, 22 Jul 2024 13:56:36 +0000
"Whelan, Andy" <awhelan-s5OS3+GPyY/[email protected]> • #4127
Re: Best strategy for calculating average synchronization time.
Fri, 19 Jul 2024 08:44:28 -0700 (PDT)
Bill Unruh <[email protected]> • #4126
Re: Re: question about the values in critical_runs array
Fri, 19 Jul 2024 07:24:58 +0000
邹林志08963 <[email protected]> • #4125
Re: Re: question about the values in critical_runs array
Fri, 19 Jul 2024 08:53:00 +0200
Miroslav Lichvar <[email protected]> • #4124
Re: Re: question about the values in critical_runs array
Fri, 19 Jul 2024 05:27:41 +0000
邹林志08963 <[email protected]> • #4123
Re: 回复: [chrony-users ] question about the values in critical_runs array
Thu, 18 Jul 2024 15:04:09 +0200
Miroslav Lichvar <[email protected]> • #4122
Re: Best strategy for calculating average synchronization time.
Wed, 17 Jul 2024 15:07:46 +0200
Miroslav Lichvar <[email protected]> • #4121
Best strategy for calculating average synchronization time.
Wed, 17 Jul 2024 12:53:47 +0000
"Whelan, Andy" <awhelan-s5OS3+GPyY/[email protected]> • #4120
Re: chrony ignoring shm source
Wed, 17 Jul 2024 14:49:02 +0200
folkert <folkert-Beo89p9qyDM6GGFevw1D/[email protected]> • #4119
Re: chrony ignoring shm source
Wed, 17 Jul 2024 14:09:06 +0200
Miroslav Lichvar <[email protected]> • #4118
chrony ignoring shm source
Wed, 17 Jul 2024 14:02:42 +0200
folkert <folkert-Beo89p9qyDM6GGFevw1D/[email protected]> • #4117
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 13:39:06 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4116
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 13:17:50 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4115
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 13:12:08 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4114
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 12:37:07 +0200
Miroslav Lichvar <[email protected]> • #4113
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 12:08:26 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4112
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 10:01:35 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4111
Re: Chrony and systemd-timesyncd
Wed, 17 Jul 2024 09:49:15 +0200
Miroslav Lichvar <[email protected]> • #4110
Re: Chrony and systemd-timesyncd
Tue, 16 Jul 2024 15:42:05 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4109
Re: Chrony and systemd-timesyncd
Tue, 16 Jul 2024 12:03:48 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4108
Re: Chrony and systemd-timesyncd
Mon, 15 Jul 2024 09:03:33 +0200
Miroslav Lichvar <[email protected]> • #4107
Re: Debugging PPS messages in chrony
Mon, 15 Jul 2024 08:58:32 +0200
Miroslav Lichvar <[email protected]> • #4106
Re: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 08:59:40 -0700
[email protected] • #4105
Re: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 17:54:38 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4104
Re: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 14:34:42 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4103
Re: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 14:23:53 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4102
RE: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 12:06:59 +0000
MUZZULINI Frank <[email protected]> • #4101
Re: Chrony and systemd-timesyncd
Fri, 12 Jul 2024 14:44:26 +0300
Andrei Borzenkov <[email protected]> • #4100
Chrony and systemd-timesyncd
Fri, 12 Jul 2024 13:32:21 +0200
Jan Claußen <jan.claussen10-S0/[email protected]> • #4099
回复: [chrony-users] question about the val ues in critical_runs array
Tue, 9 Jul 2024 11:34:04 +0000
邹林志08963 <[email protected]> • #4098
Re: Debugging PPS messages in chrony
Mon, 8 Jul 2024 19:34:29 +0200
Morten Nissov <[email protected]> • #4097
Re: Debugging PPS messages in chrony
Mon, 08 Jul 2024 13:24:41 -0400
Rob Foehl <[email protected]> • #4096
Re: Debugging PPS messages in chrony
Mon, 8 Jul 2024 19:03:30 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4095
Re: Debugging PPS messages in chrony
Mon, 8 Jul 2024 18:51:31 +0200
Morten Nissov <[email protected]> • #4094
Re: Debugging PPS messages in chrony
Mon, 8 Jul 2024 18:06:26 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4093
Debugging PPS messages in chrony
Mon, 8 Jul 2024 10:07:46 +0200
Morten Nissov <[email protected]> • #4092
Re: Seeing full FQDN in chronyc output
Wed, 26 Jun 2024 20:47:06 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4091
Re: Seeing full FQDN in chronyc output
Wed, 26 Jun 2024 14:37:11 -0400
Mike Hall <[email protected]> • #4090
Re: Seeing full FQDN in chronyc output
Wed, 26 Jun 2024 14:33:26 -0400
Josef 'Jeff' Sipek <[email protected]> • #4089
Seeing full FQDN in chronyc output
Wed, 26 Jun 2024 14:29:07 -0400
Mike Hall <[email protected]> • #4088
Re: question about the values in critical_runs array
Tue, 25 Jun 2024 09:38:09 +0000
邹林志08963 <[email protected]> • #4087
Re: question about the values in critical_runs array
Tue, 25 Jun 2024 10:35:21 +0200
Miroslav Lichvar <[email protected]> • #4086
question about the values in critical_runs array
Tue, 25 Jun 2024 01:47:27 +0000
邹林志08963 <[email protected]> • #4085
Re: Pool vs. server without config parsing
Mon, 24 Jun 2024 21:56:50 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4084
Re: Pool vs. server without config parsing
Mon, 24 Jun 2024 08:48:04 -0400
Josef 'Jeff' Sipek <[email protected]> • #4083
Re: Pool vs. server without config parsing
Mon, 24 Jun 2024 11:54:47 +0200
Miroslav Lichvar <[email protected]> • #4082
Re: Pool vs. server without config parsing
Fri, 21 Jun 2024 21:21:28 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4081
Re: Pool vs. server without config parsing
Fri, 21 Jun 2024 12:42:17 -0400
Josef 'Jeff' Sipek <[email protected]> • #4080
Re: Pool vs. server without config parsing
Fri, 21 Jun 2024 18:26:06 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4079
Pool vs. server without config parsing
Fri, 21 Jun 2024 10:05:27 -0400
Josef 'Jeff' Sipek <[email protected]> • #4078
Re: setserial low_latency - is it necessary?
Mon, 17 Jun 2024 11:47:47 +0000
Sviatoslav Feshchenko <[email protected]> • #4077
Re: setserial low_latency - is it necessary?
Mon, 17 Jun 2024 09:02:13 +0200
Miroslav Lichvar <[email protected]> • #4076
setserial low_latency - is it necessary?
Thu, 13 Jun 2024 20:22:03 +0000
Sviatoslav Feshchenko <[email protected]> • #4075
Re: Understand why system clock is bad even though chrony offsets look fine
Mon, 20 May 2024 09:32:32 -0700 (PDT)
Bill Unruh <[email protected]> • #4074
Re: Understand why system clock is bad even though chrony offsets look fine
Mon, 20 May 2024 09:20:41 -0700 (PDT)
Bill Unruh <[email protected]> • #4073
Re: Understand why system clock is bad even though chrony offsets look fine
Mon, 20 May 2024 07:21:32 -0400
Brian Cook <bcook-7C+AMPwA5wV9Og/VYhtI4QHE/[email protected]> • #4072
Re: Understand why system clock is bad even though chrony offsets look fine
Mon, 20 May 2024 11:19:14 +0200
Miroslav Lichvar <[email protected]> • #4071
Re: Understand why system clock is bad even though chrony offsets look fine
Thu, 16 May 2024 18:01:10 +0530
Abhijith Sethuraj <[email protected]> • #4070
RE: Understand why system clock is bad even though chrony offsets look fine
Wed, 15 May 2024 07:10:17 +0000
MUZZULINI Frank <[email protected]> • #4069
Re: Understand why system clock is bad even though chrony offsets look fine
Tue, 14 May 2024 06:23:49 -0700 (PDT)
Bill Unruh <[email protected]> • #4068
Re: Understand why system clock is bad even though chrony offsets look fine
Tue, 14 May 2024 13:36:42 +0200
Miroslav Lichvar <[email protected]> • #4067
Re: Understand why system clock is bad even though chrony offsets look fine
Tue, 14 May 2024 16:35:14 +0530
Abhijith Sethuraj <[email protected]> • #4066
Re: Re: Linux time goes wrong after changing the time with 'date' cmd
Mon, 13 May 2024 20:36:47 +0800
Feng Tang <[email protected]> • #4065
Re: Re: Linux time goes wrong after changing the time with 'date' cmd
Mon, 13 May 2024 04:00:33 -0700 (PDT)
Bill Unruh <[email protected]> • #4064
Re: Re: Linux time goes wrong after changing the time with 'date' cmd
Mon, 13 May 2024 16:16:04 +0800
Feng Tang <[email protected]> • #4063
Re: Re: Linux time goes wrong after changing the time with 'date' cmd
Mon, 13 May 2024 08:19:07 +0200
Miroslav Lichvar <[email protected]> • #4062
Re: Linux time goes wrong after changing the time with 'date' cmd
Mon, 13 May 2024 09:02:31 +0800
Feng Tang <[email protected]> • #4061
Re: Linux time goes wrong after changing the time with 'date' cmd
Fri, 10 May 2024 09:47:36 +0200
Rob Janssen <chrony-users-Cohe+2zZ/ftmR6Xm/[email protected]> • #4060
Linux time goes wrong after changing the time with 'date' cmd
Fri, 10 May 2024 09:43:25 +0800
Feng Tang <[email protected]> • #4059
Re: Silent Failure -- Enhancement Request
Thu, 2 May 2024 15:12:16 +0200
Miroslav Lichvar <[email protected]> • #4058
Re: SV: Update interval larger than maxpoll
Thu, 2 May 2024 11:52:52 +0200
Miroslav Lichvar <[email protected]> • #4057
SV: Update interval larger than maxpoll
Wed, 1 May 2024 10:04:22 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #4056
Re: Update interval larger than maxpoll
Mon, 29 Apr 2024 09:24:41 +0200
Miroslav Lichvar <[email protected]> • #4055
Update interval larger than maxpoll
Sun, 28 Apr 2024 09:40:27 +0000
Henning Svane <hsv-i2u8QauLV39aa/[email protected]> • #4054
RE: Silent Failure -- Enhancement Request
Mon, 22 Apr 2024 15:54:50 +0000
Chris Knox <Christopher.Knox-E0T7EY2UX4gpIyhaTEd/[email protected]> • #4053
Re: Understand why system clock is bad even though chrony offsets look fine
Mon, 22 Apr 2024 08:35:03 +0200
Miroslav Lichvar <[email protected]> • #4052
Re: Silent Failure -- Enhancement Request
Mon, 22 Apr 2024 08:29:43 +0200
Miroslav Lichvar <[email protected]> • #4051
Re: Silent Failure -- Enhancement Request
Fri, 19 Apr 2024 16:57:28 +0000
Carsten Finis <[email protected]> • #4050
RE: Silent Failure -- Enhancement Request
Fri, 19 Apr 2024 09:42:30 -0700 (PDT)
Bill Unruh <[email protected]> • #4049
Re: Silent Failure -- Enhancement Request
Fri, 19 Apr 2024 18:07:22 +0200
Holger Hoffstätte <[email protected]> • #4048
RE: Silent Failure -- Enhancement Request
Fri, 19 Apr 2024 14:40:55 +0000
Chris Knox <Christopher.Knox-E0T7EY2UX4gpIyhaTEd/[email protected]> • #4047
Re: Silent Failure -- Enhancement Request
Fri, 19 Apr 2024 11:27:52 +1200
Bryan Christianson <[email protected]> • #4046
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.