On Mon, Jun 17, 2024 at 09:14:38AM -0500, David Wright wrote:
You asked after your /system/ clock. I don't think I can tell whether
it's set to UTC or Local Time, but only that it is correct, whichever
it it on. Likewise the hardware RTC. The third line of /etc/adjtime
says what the RTC is on; /etc/timezone says what the system is on;
$ date says what your user is on.
/etc/timezone is only used by some legacy programs. All the current
ones should be using /etc/localtime instead, which is a symlink to a
binary zoneinfo file, rather than a text file containing a timezone name.
I wonder if Keith's confusion is simply due to my MUA using "AM" and "PM"
in its attribution line, and Keith not seeing the "PM". Maybe I should
look into configuring that differently.
On Mon 17 Jun 2024 at 10:23:46 (-0400), Greg Wooledge wrote:
/etc/timezone is only used by some legacy programs. All the current
ones should be using /etc/localtime instead, which is a symlink to a
binary zoneinfo file, rather than a text file containing a timezone name.
You're right of course, but confirming its value does involve using
a command that's probably not at the front of one's mind.
BTW what's the relationship between "current programs" and TZ nowadays?
On Mon 17 Jun 2024 at 10:23:46 (-0400), Greg Wooledge wrote:
I wonder if Keith's confusion is simply due to my MUA using "AM" and "PM"
in its attribution line, and Keith not seeing the "PM". Maybe I should
look into configuring that differently.
Along with 350M Americans! They even use just A and P over here. And a
mere dot on digital clocks.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (2 / 14) |
Uptime: | 147:48:10 |
Calls: | 10,383 |
Calls today: | 8 |
Files: | 14,054 |
D/L today: |
2 files (1,861K bytes) |
Messages: | 6,417,735 |