Re: System time/timezone, was Re: Maximum size .bash_aliases file
On Tue 18 Jun 2024 at 10:04:45 (+0200), tomas@tuxteam.de wrote:
> On Mon, Jun 17, 2024 at 11:54:03PM -0500, David Wright wrote:
> > On Mon 17 Jun 2024 at 19:40:30 (+0200), tomas@tuxteam.de wrote:
> > > On Mon, Jun 17, 2024 at 01:20:53PM -0400, Greg Wooledge wrote:
>
> [...]
>
> > > > Time zones are not in effect for users, either; they're in effect for
> > > > processes [...]
> > >
> > > Right you are.
> >
> > So it comes down to nomenclature.
> >
> > What should I call the timezone of my computer when it's booted up and
> > no users are logged in?
>
> [...]
>
> Most processes don't need one. When they display datetimes to a user
> timezone becomes relevant.
… which, as well as ignoring the minority that do, doesn't give me
an answer.
> > $ date; timedatectl status
> > Mon Jun 17 23:51:43 CDT 2024
> > Local time: Tue 2024-06-18 04:51:43 UTC
> > Universal time: Tue 2024-06-18 04:51:43 UTC
> > RTC time: Tue 2024-06-18 04:51:43
> > Time zone: Etc/UTC (UTC, +0000)
> > System clock synchronized: yes
> > NTP service: active
> > RTC in local TZ: no
> > $
> >
> > I notice that man timedatectl says:
> >
> > set-timezone [TIMEZONE]
> > Set the system time zone to the specified value.
> > Available timezones can be listed with list-timezones.
> > If the RTC is configured to be in the local time, this
> > will also update the RTC time. This call will alter
> > the /etc/localtime symlink. See localtime(5) for more
> > information.
>
> I cringe a bit when I see that.
See what, exactly? I can see three things, potentially.
Cheers,
David.
Reply to: