• Re: systemd and timezone (was: Re: difference in seconds between two fo

    From tomas@tuxteam.de@21:1/5 to Max Nikulin on Thu Dec 21 07:00:01 2023
    On Thu, Dec 21, 2023 at 10:30:42AM +0700, Max Nikulin wrote:

    [...]

    See systemd-timedated.service(8) and org.freedesktop.timedate1(5)

    busctl introspect org.freedesktop.timedate1 /org/freedesktop/timedate1
    # Values are stripped
    org.freedesktop.DBus.Properties interface -

    [...]

    Desktop environments use this interface.

    Ugh.

    [...]

    I would not be surprised to find an "Automatic time zone" checkbox in GUI settings similar to e.g. Android.

    Double ugh.

    UNIX got that right from the start. Now this crazy notion "the computer
    HAS to have a timezone of its own" is creeping in.

    Glad I stay clear from that "Desktop" craze. Thanks for giving me yet
    another reason :-)

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZYPOLQAKCRAFyCz1etHa RkAzAJ9km+4+nfC++9D7HKTrfJ0uvxwu/ACfT6mE1xyWUq7QaaTjQXmtWgwm0lg=
    =Vxjb
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dan Ritter@21:1/5 to Max Nikulin on Thu Dec 21 15:30:02 2023
    Max Nikulin wrote:
    I am not going to discuss code posted by Albretch, despite it has serious issues from my point of view. This is a response to Greg.

    On 20/12/2023 22:04, Greg Wooledge wrote:
    The default time zone has nothing to do with systemd, nor with any other init system that may be in place. Systemd does not know or care about
    the system's default time zone.

    See systemd-timedated.service(8) and org.freedesktop.timedate1(5)

    busctl introspect org.freedesktop.timedate1 /org/freedesktop/timedate1
    # Values are stripped
    org.freedesktop.DBus.Properties interface -
    .PropertiesChanged signal sa{sv}as org.freedesktop.timedate1 interface -
    .SetTimezone method sb
    .Timezone property s

    Desktop environments use this interface.

    Is this set per-user? Because I certainly have multiple users on
    the same computer at the same time from different timezones. And
    it is quite possible on a few of those machines to have multiple
    desktop users, each from a different TZ.

    -dsr-

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Dan Ritter on Thu Dec 21 16:10:02 2023
    On Thu, Dec 21, 2023 at 09:08:09AM -0500, Dan Ritter wrote:
    Max Nikulin wrote:
    I am not going to discuss code posted by Albretch, despite it has serious issues from my point of view. This is a response to Greg.

    On 20/12/2023 22:04, Greg Wooledge wrote:
    The default time zone has nothing to do with systemd, nor with any other init system that may be in place. Systemd does not know or care about the system's default time zone.

    See systemd-timedated.service(8) and org.freedesktop.timedate1(5)

    busctl introspect org.freedesktop.timedate1 /org/freedesktop/timedate1
    # Values are stripped
    org.freedesktop.DBus.Properties interface -
    .PropertiesChanged signal sa{sv}as org.freedesktop.timedate1 interface -
    .SetTimezone method sb
    .Timezone property s

    Desktop environments use this interface.

    Is this set per-user? Because I certainly have multiple users on
    the same computer at the same time from different timezones. And
    it is quite possible on a few of those machines to have multiple
    desktop users, each from a different TZ.

    I've sometimes the impression that desktop environments are losing
    the concept pf multi-user operating systems and are regreding to
    something like Windows 95.

    But hey. I'm just an old fart ;-)

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZYRRWgAKCRAFyCz1etHa RqaBAJ9D/lZBRr/tqWxQXh86ADOLgT9AxACfTbu7SIBPJOypKpBPLFYW0dW2LWY=
    =e94i
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From tomas@tuxteam.de@21:1/5 to Jeffrey Walton on Thu Dec 21 18:40:01 2023
    On Thu, Dec 21, 2023 at 11:04:35AM -0500, Jeffrey Walton wrote:

    [...]

    I think you will find a fair number of Unix & Linux servers set a
    default timezone. I sometimes have to set TZ in my bashrc because of
    an unexpected default timezone. Or that's been my experience at the
    GCC Compile Farm, <https://gcc.gnu.org/wiki/CompileFarm>.

    But it's not the "server's timezone". It is the default timezone for applications which haven't set one themselves (if they care about it
    at all).

    A "server's timezone" makes so much sense as a "server's $PATH setting".
    Or its $LANG.

    But I'm out of it.

    Cheers
    --
    t

    -----BEGIN PGP SIGNATURE-----

    iF0EABECAB0WIQRp53liolZD6iXhAoIFyCz1etHaRgUCZYRzbwAKCRAFyCz1etHa RtKuAJ4m4t8o9Yk4rLEPcaLGUoMumJHaWACffVSFX7h+SAyvDEC8K5DI1/snRvs=
    =VJ+A
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nicolas George@21:1/5 to All on Thu Dec 21 23:00:01 2023
    tomas@tuxteam.de (12023-12-21):
    I've sometimes the impression that desktop environments are losing
    the concept pf multi-user operating systems and are regreding to
    something like Windows 95.

    Desktop environment and the “modern” applications designed for them had already lost the ability to put back everything in place by quitting and restarting. Now they are losing the concept of multiple users, and they
    are also losing the ability to run several independent instances of the
    same program.

    Desktop environment suck.

    Regards,

    --
    Nicolas George

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)