Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #268123
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: strange time problem with bullseye |
| Date | 2024-03-07 03:40 +0100 |
| Message-ID | <IfbPP-eVFU-3@gated-at.bofh.it> (permalink) |
| References | <If3yV-eQGG-5@gated-at.bofh.it> <If8oV-eTy6-1@gated-at.bofh.it> <If8yB-eTTm-3@gated-at.bofh.it> <IfaTL-eV8P-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Mar 06, 2024 at 08:33:37PM -0500, gene heskett wrote:
> no place in the ntpsec docs, nor the chrony docs
> does it show the ability to slam the current time into the SW clock on these
> arm systems at bootup's first access time.
Traditionally, this was done by the ntpdate command, which was in the
ntpdate package.
On older Debian releases, you would install both of these (ntp and
ntpdate); ntpdate would run first, slamming the clock, and then ntp
would run second, to keep the clock in sync.
A few releases ago, ntpdate was deprecated, and its slamming functionality
was absorbed into the ntp package, as long as ntp is started with the -g
option.
-g, --panicgate
Allow the first adjustment to be big. This option may appear an
unlimited number of times.
Normally, ntpd exits with a message to the system log if the offset
exceeds the panic threshold, which is 1000 s by default. This
option allows the time to be set to any value without restriction;
however, this can happen only once. If the threshold is exceeded
after that, ntpd will exit with a message to the system log. This
option can be used with the -q and -x options. See the tinker
configuration file directive for other options.
With ntpsec replacing ntp in Debian 12, the same options apply. By default,
Debian runs ntpsec with the -g option, to allow the clock to be slammed
at boot time.
hobbit:~$ ps -ef | grep ntpd
ntpsec 854 1 0 Feb17 ? 00:01:17 /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
greg 394737 1138 0 21:34 pts/0 00:00:00 grep ntpd
Your claims that "no place in the ntpsec docs ... show the ability to
slam the current time" are simply false.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-06 06:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-06 13:10 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-06 19:10 +0100
Re: strange time problem with bullseye David Wright <deblis@lionunicorn.co.uk> - 2024-03-06 20:30 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-06 18:20 +0100
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-06 18:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-06 18:50 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 00:00 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 00:10 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 02:40 +0100
Re: strange time problem with bullseye John Hasler <john@sugarbit.com> - 2024-03-07 03:10 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 06:30 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 14:40 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 14:50 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-07 17:20 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 17:40 +0100
Re: strange time problem with bullseye Teemu Likonen <tlikonen@iki.fi> - 2024-03-07 15:10 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-07 20:40 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 20:50 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-08 18:30 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 17:00 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-07 17:40 +0100
Re: strange time problem with bullseye/buster David Wright <deblis@lionunicorn.co.uk> - 2024-03-07 18:20 +0100
Re: strange time problem with bullseye/buster gene heskett <gheskett@shentel.net> - 2024-03-08 01:20 +0100
Re: strange time problem with bullseye/buster David Wright <deblis@lionunicorn.co.uk> - 2024-03-08 03:40 +0100
Re: strange time problem with bullseye/buster gene heskett <gheskett@shentel.net> - 2024-03-08 04:30 +0100
Re: strange time problem with bullseye/buster Max Nikulin <manikulin@gmail.com> - 2024-03-08 17:20 +0100
Re: strange time problem with bullseye Greg Wooledge <greg@wooledge.org> - 2024-03-07 03:40 +0100
Re: strange time problem with bullseye <tomas@tuxteam.de> - 2024-03-07 06:30 +0100
Re: strange time problem with bullseye "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-03-07 20:20 +0100
Re: strange time problem with bullseye Dan Ritter <dsr@randomstring.org> - 2024-03-07 20:50 +0100
Re: strange time problem with bullseye gene heskett <gheskett@shentel.net> - 2024-03-08 01:30 +0100
Re: strange time problem with bullseye Jeffrey Walton <noloader@gmail.com> - 2024-03-06 18:50 +0100
csiph-web