On Tue, Mar 05, 2024 at 08:28:49PM +0800, hlyg wrote: > Thank Greg Wooledge! > > zhou@debian:~$ date > Wed 06 Mar 2024 04:07:02 AM CST > zhou@debian:~$ date -u > Tue 05 Mar 2024 08:07:07 PM UTC > > above is from deb11 for i386, it's correct
OK, and your time zone is 20 hours ahead of UTC, it appears. > zhou@debian:~$ date > Tue 05 Mar 2024 08:13:23 PM CST > zhou@debian:~$ date -u > Tue 05 Mar 2024 12:13:27 PM UTC > > above is from deb11 for amd64, it's wrong, utc lag behind by 4 hours Now this is odd-looking. In this instance, your time zone is 4 hours *behind* UTC instead of 20 hours ahead. Which makes it off by exactly one whole day. Also, it *looks* like your i386 instance wrote UTC to the system clock, and then your amd64 instance read that as local time. You can see that the 8:07:07 PM from the first instance is quite close to the 8:13:23 PM from the second. > Windows shall not cause problem, i rarely use Windows The question isn't how often you use it, but whether you booted it in between the two instances above. Probably not, I suppose. > i don't know if ntp is running, what's default configuration by deb11 amd64 > installer? There is no "default". Or rather, there are lots of defaults. It's not useful to ask about defaults. Ask about what you have. These are the packages that provide time-daemon on Debian 11: systemd-timesyncd openntpd ntp chrony If one of those is installed and running, it should set your clock from Internet sources (assuming it's configured reasonably, and you have Internet access). But more importantly, you need to check whether your Debian instances are using local time or UTC for the real time clock, because it *looks* like the i386 one is using UTC and the amd64 is not. Check your /etc/adjtime files. I'm also extremely curious why two different systems report "CST" with two wildly different offsets from UTC. What does "ls -ld /etc/localtime" give on your systems? Are they both the same?
