Tor
Active Member
- Joined
- Oct 3, 2008
- Messages
- 709
Ok DST changed last night. So what do I see on my Pandora?
WRONG TIME! And not only is the local time one hour wrong, it's much worse: 'date -u' now shows that the clock, which shall always be UTC, has somehow been moved one hour!
What's going on here? Has somebody tried to wrestle the setup to mimic Windows' buggy behaviour of old?
In case this isn't clear:
1) The hardware clock shall always run at UTC (aka GMT if you wish)
2) /etc/localtime shall be a symlink to /usr/share/zoneinfo/<your-timezone>, in my case Europe/Paris, which it in fact is. (For me, it just has to be something that is == MET, and most European cities will do.)
3) Alternatively, but less preferred, /etc/localtime could be a copy. Symlink is better. Which it is.
That's all. Linux handles it all from there. And, as 1) and 2) are actually correctly set up on my Pandora, how can it even be possible that my hardware clock is now 1 hour wrong? And my localtime too, of course, as the /etc/localtime setup is correct.
Update: Please note that I booted my Pandora from shut-off this morning. So whatever took place to utterly abuse the hardware clock may have taken place in some startup script. I don't have the means to log in remotely to peek around at the moment and working locally is tricky with the keyboard because I'm in a room with overhead lights.
WRONG TIME! And not only is the local time one hour wrong, it's much worse: 'date -u' now shows that the clock, which shall always be UTC, has somehow been moved one hour!
What's going on here? Has somebody tried to wrestle the setup to mimic Windows' buggy behaviour of old?
In case this isn't clear:
1) The hardware clock shall always run at UTC (aka GMT if you wish)
2) /etc/localtime shall be a symlink to /usr/share/zoneinfo/<your-timezone>, in my case Europe/Paris, which it in fact is. (For me, it just has to be something that is == MET, and most European cities will do.)
3) Alternatively, but less preferred, /etc/localtime could be a copy. Symlink is better. Which it is.
That's all. Linux handles it all from there. And, as 1) and 2) are actually correctly set up on my Pandora, how can it even be possible that my hardware clock is now 1 hour wrong? And my localtime too, of course, as the /etc/localtime setup is correct.
Update: Please note that I booted my Pandora from shut-off this morning. So whatever took place to utterly abuse the hardware clock may have taken place in some startup script. I don't have the means to log in remotely to peek around at the moment and working locally is tricky with the keyboard because I'm in a room with overhead lights.
Last edited by a moderator:
