On 1/31/24 21:50, Max Nikulin wrote:
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock
to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate c
On 31/01/2024 20:24, didar wrote:
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
You can us
Darac Marjal wrote:
>
>The script works like this: if the root device is specified on the
>kernel command line AND the word "fixrtc" is specified, then get the
>time that the root file system was last mounted. The script then uses
>"date" to set the clock to that date stamp.
>
>I assume that
On Wed, 2024-01-31 at 12:56 -0500, gene heskett wrote:
> [...]
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: No suitable source for initstepslew
> Dec 30 03:15:42 bpi51e5p chronyd[1936]: Could not add source 192.168.71.3
> Dec
On 1/31/24 13:19, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
# Stop bad estimates upsetting machine clock.
maxupdateskew 10.0
initstepslew 30 192.168.71.3
# This directive enables kernel synchronisation (every 11 minutes) of the
# real-time clock
On 31/01/2024 12:12, Max Nikulin wrote:
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
I think, the problem is no RTC on some *pi board, certainly c
On Wed, Jan 31, 2024 at 12:56:37PM -0500, gene heskett wrote:
[...]
> # Stop bad estimates upsetting machine clock.
> maxupdateskew 10.0
> initstepslew 30 192.168.71.3
> # This directive enables kernel synchronisation (every 11 minutes) of the
> # real-time clock. Note that it can’t be used alo
On 1/31/24 10:44, Greg Wooledge wrote:
On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
On 1/31/24 08:53, John Hasler wrote:
Gene writes:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
initstepslew
ma
On Wed, Jan 31, 2024 at 10:25:40AM -0500, gene heskett wrote:
> On 1/31/24 08:53, John Hasler wrote:
> > Gene writes:
> > > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > > the current time on the first cycle as its rebooting?
> >
> > initstepslew
> >
> > man chrony.co
On 1/31/24 08:53, John Hasler wrote:
Gene writes:
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
deprecated in favor of makestep, and did not work, John.
Thanks, John
Cheers, Gene He
Max Nikulin wrote:
> I think, the problem is no RTC on some *pi board, certainly chrony out of
> box setup is not ready to such environment and its solution is not
> maxstep.
That's what makestep (initstepslew now being deprecated) is for.
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On 1/31/24 07:13, Max Nikulin wrote:
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
Well, I do have other probs with that machine, mostly with the phys
On Wed, Jan 31, 2024 at 07:53:01AM -0600, John Hasler wrote:
> Gene writes:
> > How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> > the current time on the first cycle as its rebooting?
>
> initstepslew
>
> man chrony.conf
Debian 12 has chrony 4.3, and in *that* version of
Gene writes:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to
> the current time on the first cycle as its rebooting?
initstepslew
man chrony.conf
--
John Hasler
j...@sugarbit.com
Elmwood, WI USA
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other
On 31/01/2024 17:54, to...@tuxteam.de wrote:
I think you want "maxstep". It's in the man page chrony.conf(5).
But if the time is "months off" perhaps you've got another problem
to fix first?
I think, the problem is no RTC on some *pi board, certainly chrony out
of box setup is not ready to su
On Wed, Jan 31, 2024 at 05:32:26AM -0500, gene heskett wrote:
> How do I setup /etc/chrony/chrony.conf so it slams the system clock to the
> current time on the first cycle as its rebooting?
> There was 20 yeas back, an ntpdate command that would do that.
> Now it appears to conflict with the other
How do I setup /etc/chrony/chrony.conf so it slams the system clock to
the current time on the first cycle as its rebooting?
There was 20 yeas back, an ntpdate command that would do that.
Now it appears to conflict with the other client/servers
Thanks
Cheers, Gene Heskett, CET.
--
"There are fo
18 matches
Mail list logo
