Quote:
Originally Posted by maddy0
Hello, thanks for posting, these the results:
root@xxx:/home/tony# sudo setenv TZ Europe/Rome
sudo: setenv: command not found
root@xxx:/home/tony# export TZ="Europe/Rome"
root@xxxx:/home/tony# timedatectl | grep local
RTC in local TZ: no
root@Nxxx:/home/tony# timedatectl
Local time: Sat 2023-12-09 09:29:56 WET
Universal time: Sat 2023-12-09 09:29:56 UTC
RTC time: Sat 2023-12-09 09:29:56
Time zone: Europe/Lisbon (WET, +0000)
System clock synchronized: yes
NTP service: n/a
RTC in local TZ: no
I already tryed:
sudo dpkg-reconfigure tzdata ;(
|
I do not know what timedatectl is or does, the distro I use does not have it. I never needed it.
When setting TZ, you never need to change the actual hardware system clock. But as I mentioned, Linux Desktop Environments seems to require a M/S Windows date/time set action.
For example, in a terminal try this, you can see the date/time displayed is controlled by $TZ:
Code:
magnetar % locate timedatect
% setenv TZ Europe/Rome
% date
Sat Dec 9 15:16:54 CET 2023
% setenv TZ America/Los_Angeles
% date
Sat Dec 9 06:17:03 PST 2023
% setenv TZ America/New_York
% date
Sat Dec 9 09:17:18 EST 2023
Note, I do not use bash, but the above will work with bash. If it does not work, your distro does something odd with its TZ package.
If I set TZ to "Europe/Rome" in ~/.xsession (or ~/.xinitrc) and start fvwm, xclocks and all other clocks shows the Time as it exists in Rome. No need for a system clock change or timedatectl.
HTH a bit