Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #268092
| Path | csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Greg Wooledge <greg@wooledge.org> |
| Newsgroups | linux.debian.user |
| Subject | Re: strange time problem with bullseye |
| Date | Wed, 06 Mar 2024 13:10:01 +0100 |
| Message-ID | <IeYfT-eNFL-13@gated-at.bofh.it> (permalink) |
| References | <IeJ7b-eEa0-9@gated-at.bofh.it> <IeSat-eJTp-1@gated-at.bofh.it> |
| X-Original-To | debian-user@lists.debian.org |
| X-Mailbox-Line | From debian-user-request@lists.debian.org Wed Mar 6 12:08:03 2024 |
| Old-Return-Path | <greg@wooledge.org> |
| X-Amavis-Spam-Status | No, score=-4.557 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, RDNS_NONE=0.793, SARE_MLH_Stock10=1.66, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -4.6 |
| Mail-Followup-To | debian-user@lists.debian.org |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=us-ascii |
| Content-Disposition | inline |
| X-Mailing-List | <debian-user@lists.debian.org> archive/latest/810020 |
| List-ID | <debian-user.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-user/> |
| List-Archive | https://lists.debian.org/msgid-search/ZehciLfvT8JYbNkG@wooledge.org |
| Approved | robomod@news.nic.it |
| Lines | 22 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Wed, 6 Mar 2024 07:07:36 -0500 |
| X-Original-Message-ID | <ZehciLfvT8JYbNkG@wooledge.org> |
| X-Original-References | <TYSPR02MB83823B8127D624773C2DEE9BC5222@TYSPR02MB8382.apcprd02.prod.outlook.com> <878r2v7wfu.fsf@iki.fi> |
| Xref | csiph.com linux.debian.user:268092 |
Show key headers only | View raw
On Wed, Mar 06, 2024 at 07:37:09AM +0200, Teemu Likonen wrote:
> It seems that you have solved the problem but here is another hint.
> "timedatectl" is a good high-level tool for querying and adjusting time
> settings. Without command-line arguments it prints a lot of useful info:
>
> $ timedatectl
> Local time: ke 2024-03-06 07:33:00 EET
> Universal time: ke 2024-03-06 05:33:00 UTC
> RTC time: ke 2024-03-06 05:33:00
> Time zone: Europe/Helsinki (EET, +0200)
> System clock synchronized: yes
> NTP service: active
> RTC in local TZ: no
>
> See "timedatectl -h" or manual page for more info.
This is a great hint, but be warned that it doesn't quite know about
NTP services other than systemd-timesyncd. If you're running ntpsec,
for example, it'll simply say:
System clock synchronized: yes
NTP service: n/a
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