Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #201188
| From | Long Wind <longwind2@yahoo.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | (solved) Re: jessie and stretch time problem |
| Date | 2018-10-13 09:30 +0200 |
| Message-ID | <wImx3-38T-7@gated-at.bofh.it> (permalink) |
| References | <wIdN8-6t7-9@gated-at.bofh.it> <wIdN8-6t7-7@gated-at.bofh.it> <wImnn-35N-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Thank Teemu Likonen!
You are right. My stretch and jessie think differently about hardware clock. i run "timedatectl set-local-rtc 1", it should be ok for both now.
though there's warning, i think it's ok
On Saturday, October 13, 2018 3:10 PM, Teemu Likonen <tlikonen@iki.fi> wrote:
Long Wind [2018-10-12 21:59:40Z] wrote:
> jessie and stretch are installed on same PCtime of jessie is wrong:
> Fri Oct 12 21:51:05 CST 2018then i reboot and enter stretch time of
> stretch is right: Sat Oct 13 05:55:30 CST 2018 tzdata of both are
> reconfig to same place
As others have pointed out probably one operating system thinks that the
hardware clock is in UTC time and other thinks the clock is in local
time.
You can check and configure this with "timedatectl" command. Running the
command without parameters will show the current status. Command
"timedatectl set-local-rtc [...]" (executed as root user) sets the
option in question. Command's man page tells more.
--
/// Teemu Likonen - .-.. <https://keybase.io/tlikonen> //
// PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 ///
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
jessie and stretch time problem Long Wind <longwind2@yahoo.com> - 2018-10-13 00:10 +0200
Re: jessie and stretch time problem Kenneth Parker <sea7kenp@gmail.com> - 2018-10-13 00:20 +0200
Re: jessie and stretch time problem Long Wind <longwind2@yahoo.com> - 2018-10-13 00:40 +0200
Re: jessie and stretch time problem Kenneth Parker <sea7kenp@gmail.com> - 2018-10-13 00:50 +0200
Re: jessie and stretch time problem <tomas@tuxteam.de> - 2018-10-13 08:30 +0200
Re: jessie and stretch time problem Long Wind <longwind2@yahoo.com> - 2018-10-13 09:20 +0200
Re: jessie and stretch time problem <tomas@tuxteam.de> - 2018-10-14 09:50 +0200
Re: jessie and stretch time problem Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-10-14 15:30 +0200
Re: jessie and stretch time problem Reco <recoverym4n@enotuniq.net> - 2018-10-14 16:30 +0200
Re: jessie and stretch time problem Brian <ad44@cityscape.co.uk> - 2018-10-14 20:20 +0200
Re: jessie and stretch time problem Reco <recoverym4n@enotuniq.net> - 2018-10-14 20:40 +0200
Re: jessie and stretch time problem Brian <ad44@cityscape.co.uk> - 2018-10-14 21:40 +0200
Re: jessie and stretch time problem Teemu Likonen <tlikonen@iki.fi> - 2018-10-13 09:20 +0200
(solved) Re: jessie and stretch time problem Long Wind <longwind2@yahoo.com> - 2018-10-13 09:30 +0200
Re: (solved) Re: jessie and stretch time problem David Wright <deblis@lionunicorn.co.uk> - 2018-10-13 16:10 +0200
Re: (solved) Re: jessie and stretch time problem Brian <ad44@cityscape.co.uk> - 2018-10-13 21:00 +0200
Re: (solved) Re: jessie and stretch time problem Curt <curty@free.fr> - 2018-10-13 22:00 +0200
Re: (solved) Re: jessie and stretch time problem David Wright <deblis@lionunicorn.co.uk> - 2018-10-13 23:00 +0200
csiph-web