Problems to set time and conflict with debian systems

Topic: Problems to set time and conflict with debian systems (Read 7497 times) previous topic - next topic

0 Members and 3 Guests are viewing this topic.

Problems to set time and conflict with debian systems

23 December 2017, 18:58:53

Hi,

Time change in Artix when i go from archs to debian systems. Windows is not installed. Date is o”k in debians.

When i run the command timedatectl it is responding that it do not exist ... How to set time here?.

I'm just traying to do something:

Code: [Select]

[[kaos keos]# LANG=C pacman -S tzdata
warning: tzdata-2017c-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) tzdata-2017c-1

Total Installed Size:  1.82 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) reinstalling tzdata                          [######################] 100%
[kaos keos]# LANG=C timedatectl set-timezone America/Newyork
bash: timedatectl: no se encontró la orden
[kaos keos]# 

it is saying that this command do not exist./code]

Thanks.

Re: Problems to set time and conflict with debian systems

Reply #1 – 23 December 2017, 19:08:14

I use "timeset-gui" from the AUR works well for me.

Re: Problems to set time and conflict with debian systems

Reply #2 – 23 December 2017, 20:46:52

it works.

thank you very much!

Re: Problems to set time and conflict with debian systems [solved]

Reply #3 – 24 December 2017, 13:13:39

The canonical way of setting the time zone in UNIX/LINUX is by symlinking /etc/localtime to the respective timezone info file.

Code: [Select]

# ln -sf /usr/share/zoneinfo/Europe/Athens /etc/localtime

Re: Problems to set time and conflict with debian systems [solved]

Reply #4 – 26 December 2017, 01:34:19

I've had the same problem with arch and non-arch distros fighting the hw clock or misinterpreting it.
Ok, I set the tz as you said, next day I boot up and it is 2hrs off.

If I don't boot the other system it stays where it is. When I set it here and go to the other the other one is off.
I must try the same command on that one.

Re: Problems to set time and conflict with debian systems [solved]

Reply #5 – 26 December 2017, 10:35:41

The 2-hour offset suggests the UTC-EET difference is applied on your localtime. Ergo, one of the two systems stores localtime in RTC instead of UTC.

Re: Problems to set time and conflict with debian systems [solved]

Reply #6 – 26 December 2017, 13:23:56

Does not surprise me. If I remember correctly ubuntu and debian during install if they detect windows use rtc instead of utc.

Re: Problems to set time and conflict with debian systems [solved]

Reply #7 – 26 December 2017, 16:10:14

Back again ... once i turn off the PC and change to Debian and comeback to Arch , the time is wrong again ...

i tray to install timedatectl-restorer but there are some problem with PGP 1D1F0DC78F173680

The result from option nano /etc/localtime is not given anything understandable:

Code: [Select]

GNU nano 2.9.1 /etc/localtime

TZif2^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^E^@^@^@^E^@^@^@^@^@^@^@�^@^@^@^E^@^@^$
@p��9`ˈ�p�#�p�`��u��@��U�� 5��^@��^U��p��e��މpݩ�` kp߉d`��Mp�iF`$
��`^K��p^L٢�
�gp^N��^O��^P�f�^Q�e�^RyH�^SiG�^TY*�^UI)�^V9^L�^W)^K�^X")`^Y^H��^Z^B^K`^Z�
p^[��`^\��p^]��`^^��p^_��` v^@�!��`"U��#j��$5��%J��&^U��'*s�'��p)
U�)ޥp*�7�+��p,�T`-�ip.�6`/~Kp0�^X`1gg�2r�`3GI�4R�`5'+�62�`7^G
�8^[��8��9��:��;۞�<��p=��>��p?�b�@o�pA�^?`BO�pCda`D/vpEDC`E��G-_�Gӊ�I
A�I�l�J�#�K��pL�@`M|kpN�"`O\MpP�^D`Q</pRu�`S^\^QpTU�`T��pV5�`V�^O�X^^��X��Y��$
xpeG/`e�Zpg'^Q`g�<pi^F�`i�^^pj��`k�:�l��mv^\�n��oU��p��q5��ro��s^U��tOy�t��p$
@p��9`��ˈ�p��#�p��`��u��@��U�� 5��^$
��`^@^@^@^@^K��p^@^@^@^@^L٢�^@^@^@^@
�gp^@^@^@^@^N��^@^@^@^@^O��^@^@^@^@^P�f�^@^@^@^@^Q�e�^@^@^@^@^RyH�^@^@^@^@^Si$
p^@^@^@^@^[��`^@^@^@^@^\��p^@^@^@^@^]��`^@^@^@^@^^��p^@^@^@^@^_��`^@^@^@^@ v^@�$
U�^@^@^@^@)ޥp^@^@^@^@*�7�^@^@^@^@+��p^@^@^@^@,�T`^@^@^@^@-�ip^@^@^@^@.�6`^@^@^@$
�^@^@^@^@8^[��^@^@^@^@8��^@^@^@^@9��^@^@^@^@:��^@^@^@^@;۞�^@^@^@^@<��p^@^@^@$
A�^@^@^@^@I�l�^@^@^@^@J�#�^@^@^@^@K��p^@^@^@^@L�@`^@^@^@^@M|kp^@^@^@^@N�"`^@^@^$
xp^@^@^@^@eG/`^@^@^@^@e�Zp^@^@^@^@g'^Q`^@^@^@^@g�<p^@^@^@^@i^F�`^@^@^@^@i�^^p^@$
EST5EDT,M3.2.0,M11.1.0

Re: Problems to set time and conflict with debian systems [solved]

Reply #8 – 26 December 2017, 20:28:36

finally i can install timedatectl-restorer but but i don't know what to do with:

Code: [Select]

[kaos keos]# LANG=C timedatectl-restorer 
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]#

Re: Problems to set time and conflict with debian systems

Reply #9 – 27 December 2017, 14:39:52

timedatectl-restorer -h should tell you what -r and -a do and perhaps also s

Re: Problems to set time and conflict with debian systems

Reply #10 – 27 December 2017, 16:24:26

I let ntpd set it

but hwclock works

[www3 ~]# hwclock
2017-12-27 10:22:47.327226-0500

Re: Problems to set time and conflict with debian systems

Reply #11 – 27 December 2017, 16:27:08

tzselect - and yes I remember this not working correctly on the install. I'm trying to remember if I needed to change permisions with ntpd. I remember it was tangled. Time Zone itself, that selection software has changed over the last 2 years or so. And the time zone packages themselves had to be reworked after the changle to day light saving time dates. I had to fix it all post install.

Re: Problems to set time and conflict with debian systems

Reply #12 – 27 December 2017, 16:35:00

Quote from: nous – on 26 December 2017, 10:35:41

The 2-hour offset suggests the UTC-EET difference is applied on your localtime. Ergo, one of the two systems stores localtime in RTC instead of UTC.

or his HW Clock is set to the mountain time zone?

Re: Problems to set time and conflict with debian systems

Reply #13 – 27 December 2017, 17:03:27

Code: [Select]

[kaos keos]# timedatectl-restorer -h 
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile

Restore system time across reboots when the internal clock is dead.

positional arguments:
  timefile       The file in which to save the clock time.
  runfile        The run file to use to prevent multiple restorations in a
                 single session.

optional arguments:
  -h, --help     show this help message and exit
  -r, --restore  Restore time from file. If not set, the current time will be
                 saved instead. If the run file exists or the time file does
                 not exist then no restoration will be performed.
  -a s, --add s  The number of seconds to add to the saved time. Default: 10
                 s.
[kaos keos]# timedatectl-restorer -r
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]# timedatectl-restorer -a
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: argument -a/--add: expected one argument
[kaos keos]# timedatectl-restorer -s
usage: timedatectl-restorer [-h] [-r] [-a s] timefile runfile
timedatectl-restorer: error: the following arguments are required: timefile, runfile
[kaos keos]#

Code: [Select]

[kaos keos]# hwclock 
2017-12-27 06:12:17.139733-0500
[kaos keos]# date
mié dic 27 11:12:28 EST 2017
[kaos keos]#

Re: Problems to set time and conflict with debian systems

Reply #14 – 27 December 2017, 20:26:28

Just symlink your timezone info file to /etc/localtime. It's what tzselect and that abomination from systemd do anyway.

Debian needs to be setup to store time in UTC.

Quote from: mrbrklyn – on 27 December 2017, 16:35:00

or his HW Clock is set to the mountain time zone?

He's in south-eastern Europe.