On Tue 18 Jun 2024 at 07:07:36 (-0400), Greg Wooledge wrote: > On Mon, Jun 17, 2024 at 23:54:03 -0500, David Wright wrote: > > What should I call the timezone of my computer when it's booted up and > > no users are logged in? > > Daemons will almost always use the system's default time zone (the one > specified by /etc/localtime or /etc/timezone). > > It's *theoretically* possible for some daemons to be configured to use > a different time zone, or to be hard-coded to use UTC. I've never seen > this, but it could be done.
In view of that, I think it's reasonable to drop the "default", and go with "system time zone", ie the time zone that the system clock it set to. > Usually a daemon's time zone will only affect log messages that it > writes. It's uncommon for a daemon process to use a time zone for > anything other than timestamping messages. Of course, it depends on > the individual daemon. Well, it's anything related to time, I suppose, like cron, systemd timers, clock displays, and so on. I just don't understand the idea of a computer not having a system time in a time zone. (And I'm leaving aside any connected devices, filesystems, etc that might handle times, but only in a single, local time.) Cheers, David.
