You are not logged in.
I'm in Central time. Well in the middle of it so there's no confusion. System clock has been fine but this evening out of nowhere my system decided that my time zone was now Eastern. I changed our router but made no other config changes in my Arch system at all. It just decided (via network time) that I was now in Eastern time zone.
Any thoughts on why this might be? I've googled the problem but all the answers basically assumed I was setting the UTC incorrectly (not true) or gave answers that are no longer relevant post systemd migration.
Last edited by hooya (2015-02-17 19:47:36)
Offline
Does /etc/localtime link to the correct time zone?
Offline
No, it says EST, which is incorrect. Should be CST.
Offline
Just link /etc/localtime to the appropriate file in /usr/share/zoneinfo.
Offline
I'm currently setting it manually so at least my clock is right.
But that doesn't really answer the original question. I quite literally was sitting here doing my work when an alert bubble popped up on my screen that told me that the time zone was now set to EST. Why would the network time be improperly determining my time zone.
This also happened a few months back on my wife's laptop also running Arch. thought it was a fluke and also set the time zone manually instead of via network. Since this is now two computers that it's happening to I want to see what the root cause might be.
Offline
I would assume you'd need to determine what service (broadly speaking, not necessarily a systemd .service) is at work and then find out how to debug it.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
NTP works with UTC and doesn't care where you are. Usually one sets the timezone manually, but apparently DHCP can be used to communicate timezone information, so that could be related to the router change.
Offline
NTP works with UTC and doesn't care where you are. Usually one sets the timezone manually, but apparently DHCP can be used to communicate timezone information, so that could be related to the router change.
I suspect this is the problem. My new router/cable modem has been giving me all sorts of headaches. Never buying Netgear again.
I'll mark this solved as it appears not to be an Arch specific problem and I've managed an appropriate workaround I guess. Still a bit of a mystery.
Offline