Hey Dumas!
On Tue, 01 Apr 2025 14:37:40 -0500, you wrote:
DW> I am running debian. Sometime in the past month, when I received a
DW> kernel upgrade and also a tzdata upgrade, I noticed that the time was wrong
DW> on my system.
DW> /etc/localtime -> pointed as shortcut to correct timezone
DW> /etc/timezone -> contained the correct timezone
This might depend on if you're using systemd or not. In my case (Archlinux), I
have '/etc/localtime' which is symlinked to the correct timezone in
'/usr/share/zoneinfo'. I don't have '/etc/timezone', and I use ntpd to keep my
time synced.
I disabled systemd-timesyncd awhile back, due to my clock being off at some
point, but I don't remember exactly when. It was definitely much longer ago
(months/years probably) than what you're encountering recently.
Seeing as how you're using Debian and Devuan (one can only assume here that one
has systemd and the other does not, since you didn't specify), you may want to
check to see if 'ntpd' is installed and running properly:
systemd command:
$ sudo systemctl status ntpd.service
¿ ntpd.service - Network Time Service
Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; preset:
disabled)
Active: active (running) since Mon 2025-03-31 17:58:44 CDT; 24h ago
journalctl (logs):
Mar 31 17:58:53 reaper ntpd[422]: new interface(s) found: waking up resolver
On non-systemd you probably have to do something like: 'sudo service ntpd
status' or some such. It's been awhile since I've used sysvinit.
DW> This is happening on every debian/devuan/raspbian system that I have,
DW> and it started happening sometime during the past month or six weeks
DW> after I received a kernel/tzdata update.
Does tzdata actually do anything, though? Pretty sure it simply just provides
the time zone information needed for all other applications or runtimes in the
operating system to print local time correctly. I can't imagine tzdata is to
blame, here.. unless the Debian maintainers completely jacked that package up,
and for Debian variants only.
When you type 'sudo hwclock' what do you see? Is it displaying the correct
timezone offset? And does it match your results for the 'date' command?
Here (and yes I did them a couple minutes apart ;)):
$ sudo hwclock
2025-04-01 19:37:40.996551-05:00
$ date
Tue Apr 1 07:39:28 PM CDT 2025
DW> I thought the time zone was saved in the two above places in /etc. Is
DW> there some other place that tzdata is reading from that I need to look
DW> at so that, in future, whenever tzdata gets updated I don't have to
DW> remember to go back and manually fix the time zone each time?
Those are probably the two most common places, but might vary slightly between
distros. I think tzdata is what is read (by other applications), and doesn't do
any reading of anything on it's own (but I could be wrong). I can't imagine this
is tzdata's fault, though, or it would be all over the Linux interwebz since
it's a pretty important package, and not just specific to you.
If you don't have some kind of application or service setup to sync and retain
your time and timezone information, I recommend using one.
Regards,
Nick
... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20240604
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (723:1/1)
■ Synchronet ■ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
|
