Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #265210

Re: mktime (was: Re: systemd and timezone)

From Jeffrey Walton <noloader@gmail.com>
Newsgroups linux.debian.user
Subject Re: mktime (was: Re: systemd and timezone)
Date 2023-12-23 19:30 +0100
Message-ID <HOeV3-fDS6-3@gated-at.bofh.it> (permalink)
References (8 earlier) <HNsQq-f6ZG-17@gated-at.bofh.it> <HNN8t-fjnQ-5@gated-at.bofh.it> <HNNUR-fjUz-7@gated-at.bofh.it> <HNTQB-fntj-9@gated-at.bofh.it> <HOdvX-fCUX-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Sat, Dec 23, 2023 at 11:56 AM Max Nikulin <manikulin@gmail.com> wrote:
>
> On 23/12/2023 02:41, Jeffrey Walton wrote:
> > I've found lack of per-thread timezones and libc's inability to
> > convert time between timezones a bigger problem than other issues,
> > like explicitly setting a timezone for a process.
>
>  From my point of view the TZ environment variable makes timezone
> conversion a rather expensive operation. Some libc limitations are
> highlighted in
> https://data.iana.org/time-zones/theory.html#POSIX
>
> > The use case is, an appointment needs to be added to a database with
> > UTC time, but the sender of the appointment uses localtime+timezone
> > offset, like 1:00 PM PST or 1:00 PM EST. Trying to convert the
> > localtime+timezone time to UTC (or other timezone) on a server in a
> > thread is a real nightmare. Also see
> > <https://sourceware.org/pipermail/libc-help/2021-January/005652.html>.
>
>  From that message:
> >   * given: '15 Jan 2021 01:24:55 -0800 (PST)
>
> Time zone offset is given, so the timestamp can be unambiguously
> converted to UTC or seconds since epoch.
>
> If the DB is Postgres then I would delegate timezone-related
> computations to it.
>
> Posting code that can not be compiled may hide real issue.
>
> A couple of issues that may lead to undefined behavior:
>
> (info "(libc) Low-Level Time String Parsing")
> https://www.gnu.org/software/libc/manual/html_node/Low_002dLevel-Time-String-Parsing.html#index-strptime
> >    • Before calling the ‘strptime’ function for a new input string, you
> >      should prepare the TM structure you pass.  Normally this will mean
> >      initializing all values to zero.  Alternatively, you can set all
> >      fields to values like ‘INT_MAX’, allowing you to determine which
> >      elements were set by the function call.  Zero does not work here
> >      since it is a valid value for many of the fields.
>
> Before calling mktime set tm_isdst to negative value if you do not know
> if DST is effective that moment.
>
> However being aware of tm_gmtoff GNU extension, I was not expected the
> following:
>
> (info "(libc) Broken-down Time")
> https://www.gnu.org/software/libc/manual/html_node/Broken_002ddown-Time.html#index-mktime
> >      The ‘mktime’ function ignores the specified contents of the
> >      ‘tm_wday’, ‘tm_yday’, ‘tm_gmtoff’, and ‘tm_zone’ members of the
> >      broken-down time structure.  It uses the values of the other
> >      components to determine the calendar time; it’s permissible for
> >      these components to have unnormalized values outside their normal
> >      ranges.  The last thing that ‘mktime’ does is adjust the components
> >      of the BROKENTIME structure, including the members that were
> >      initially ignored.
>
> So before calling mktime you need to set a timezone having offset of
> -0800. I have not figured out if the following approach may give
> incorrect results for some corner cases:
>
> - save tm_gmtoff from strptime results
> - set UTC timezone
> - call mktime
> - adjust result by saved tm_gmtoff
>
> Besides performance penalty due to tzset() I would not call it "nightmare".
>
> Beware with real timezones having DST or other time transitions. GNU
> libc implementation of mktime may give different results for the same
> passed argument depending of argument used for previous call.
>
> I would consider using some other library instead of libc:
> - std::chrono (I have heard of other C++ libraries created before chrono
> was added to the standard)
> - Qt
> - timelib C library from PHP
>
> P.S.
> https://stackoverflow.com/questions/11004273/what-is-stdpromise
> > std::broken_promise is the best named identifier in the standard
> > library. And there is no std::atomic_future.
> >  – Cubbi Jun 12, 2012 at 22:26
> struct tm is referred to as "Broken-down" time

Here's what someone on the libc mailing list suggested:
<https://sourceware.org/pipermail/libc-help/2021-February/005657.html>.
I'm not sure why threading broke in Mailman, so the thread could not
be followed. I should have posted it with the original email I sent.

The person offered some sample code, and stated there's no way to
avoid the [thread-unsafe] putenv with TZ. Also note that it does not
handle a source timezone string like '15 Jan 2021 01:24:55 -0800
(PST)'. You have to manually set TZ=America/California [?] first. It
is not clear to me why the part of the timezone string "-0800 (PST)"
is discarded when creating the time structure.

The person also suggested using Gnulib. My project was not using
Gnulib, so it was not an option.

I think what C programmers need is a libtz that works as expected. And
it needs to behave exactly like libc so there are no hard to track
down bugs.

Jeff

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 11:20 +0100
  Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-17 12:00 +0100
    Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 12:10 +0100
      Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 16:30 +0100
        Re: difference in seconds between two formatted dates ... "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-17 17:00 +0100
        Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 17:10 +0100
        Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-17 17:40 +0100
          Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-17 23:50 +0100
          Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 00:10 +0100
            Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 01:40 +0100
              Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 02:20 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 07:00 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-18 07:10 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 13:20 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-18 14:10 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 14:20 +0100
                date can't parse its own output was: difference in seconds between  two formatted dates ...) <tomas@tuxteam.de> - 2023-12-18 14:40 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-18 19:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-18 20:20 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-20 07:10 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 08:40 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-21 06:00 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-21 06:40 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 02:30 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 13:20 +0100
                RTC and (old) Windows [was: difference in seconds between two  formatted dates ...] <tomas@tuxteam.de> - 2023-12-21 13:30 +0100
                Re: RTC and (old) Windows [was: difference in seconds between two  formatted dates ...] David Christensen <dpchrist@holgerdanske.com> - 2023-12-21 23:30 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 02:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-22 04:10 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-20 08:50 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-20 13:20 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 13:40 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-20 14:20 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-20 14:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-20 16:10 +0100
                Re: difference in seconds between two formatted dates ... Nicolas George <george@nsup.org> - 2023-12-20 16:30 +0100
                systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) Max Nikulin <manikulin@gmail.com> - 2023-12-21 04:50 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) <tomas@tuxteam.de> - 2023-12-21 07:00 +0100
                Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-21 17:10 +0100
                Re: systemd and timezone Nicholas Geovanis <nickgeovanis@gmail.com> - 2023-12-22 02:00 +0100
                Re: systemd and timezone Andy Smith <andy@strugglers.net> - 2023-12-22 13:50 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) Jeffrey Walton <noloader@gmail.com> - 2023-12-21 17:30 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) tomas@tuxteam.de - 2023-12-21 18:40 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) Dan Ritter <dsr@randomstring.org> - 2023-12-21 15:30 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) <tomas@tuxteam.de> - 2023-12-21 16:10 +0100
                Re: systemd and timezone (was: Re: difference in seconds between two  formatted dates ...) Nicolas George <george@nsup.org> - 2023-12-21 23:00 +0100
                Re: systemd and timezone gene heskett <gheskett@shentel.net> - 2023-12-22 01:00 +0100
                Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-22 13:50 +0100
                Re: systemd and timezone <tomas@tuxteam.de> - 2023-12-22 14:40 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 15:20 +0100
                Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 16:50 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 17:30 +0100
                Re: systemd and timezone "Arno Lehmann, ITS" <al@its-lehmann.de> - 2023-12-22 20:20 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 21:00 +0100
                Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-22 20:50 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 21:20 +0100
                Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 07:20 +0100
                Re: systemd and timezone Sven Joachim <svenjoac@gmx.de> - 2023-12-22 21:20 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-22 22:40 +0100
                Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 00:30 +0100
                Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 00:50 +0100
                Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 01:10 +0100
                Re: systemd and timezone David Wright <deblis@lionunicorn.co.uk> - 2023-12-23 07:20 +0100
                Re: Support for SysV service scripts deprecated in systemd 255 (was:  systemd and timezone) Felix Miata <mrmazda@earthlink.net> - 2023-12-23 08:10 +0100
                Re: systemd and timezone Pocket <pocket@columbus.rr.com> - 2023-12-23 12:10 +0100
                Re: systemd and timezone Nate Bargmann <n0nb@n0nb.us> - 2023-12-23 02:00 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2023-12-23 02:20 +0100
                Re: systemd and timezone <tomas@tuxteam.de> - 2023-12-22 17:10 +0100
                Re: systemd and timezone Jeffrey Walton <noloader@gmail.com> - 2023-12-22 21:00 +0100
                Re: systemd and timezone Nicolas George <george@nsup.org> - 2023-12-22 23:40 +0100
                Re: systemd and timezone Charles Kroeger <mbone@gmx.co.uk> - 2024-01-06 03:30 +0100
                Re: systemd and timezone Greg Wooledge <greg@wooledge.org> - 2024-01-06 05:30 +0100
                Re: systemd and timezone gene heskett <gheskett@shentel.net> - 2024-01-06 06:40 +0100
                tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 07:20 +0100
                Re: tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 08:10 +0100
                Re: tzdata-legacy [was: Re: systemd and timezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-06 10:20 +0100
                Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 13:10 +0100
                Re: tzdata-legacy [was: Re: systemd and timezone] Greg Wooledge <greg@wooledge.org> - 2024-01-06 16:10 +0100
                Re: tzdata-legacy [was: Re: systemd and timezone] David Wright <deblis@lionunicorn.co.uk> - 2024-01-07 18:30 +0100
                was: Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 13:00 +0100
                Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] John Hasler <john@sugarbit.com> - 2024-01-06 15:30 +0100
                SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd and  timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 20:10 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemd  and timezone] John Hasler <john@sugarbit.com> - 2024-01-06 20:40 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand  timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 21:40 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand  timezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-06 23:10 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re: systemdand  timezone] Greg Wooledge <greg@wooledge.org> - 2024-01-07 01:10 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re:  systemdandtimezone] gene heskett <gheskett@shentel.net> - 2024-01-07 05:30 +0100
                Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy [was: Re:  systemdandtimezone] Nate Bargmann <n0nb@n0nb.us> - 2024-01-07 12:30 +0100
                Re: SOLVED FOR GENE Felix Miata <mrmazda@earthlink.net> - 2024-01-07 12:40 +0100
                Re: SOLVED FOR GENE jeremy ardley <jeremy.ardley@gmail.com> - 2024-01-07 13:10 +0100
                Re: SOLVED FOR GENE john doe <johndoe65534@mail.com> - 2024-01-07 13:40 +0100
                Re: SOLVED FOR GENE Michael Stone <mstone@debian.org> - 2024-01-11 14:30 +0100
                Re: SOLVED FOR GENE Felix Miata <mrmazda@earthlink.net> - 2024-01-11 18:10 +0100
                manpages package [WAS Re: SOLVED FOR GENE:Re: was: Re: tzdata-legacy  [was: Re: systemd and timezone] "Andrew M.A. Cater" <amacater@einval.com> - 2024-01-06 23:50 +0100
                Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] Max Nikulin <manikulin@gmail.com> - 2024-01-06 18:10 +0100
                Re: was: Re: tzdata-legacy [was: Re: systemd and timezone] gene heskett <gheskett@shentel.net> - 2024-01-06 20:40 +0100
                systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-07 16:50 +0100
                Re: systemd-timesyncd John Hasler <john@sugarbit.com> - 2024-01-07 17:30 +0100
                Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-07 21:20 +0100
                Re: systemd-timesyncd Charles Kroeger <mbone@gmx.co.uk> - 2024-01-08 06:50 +0100
                Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-07 21:10 +0100
                Re: systemd-timesyncd "Andrew M.A. Cater" <amacater@einval.com> - 2024-01-07 22:00 +0100
                Re: systemd-timesyncd Charles Curley <charlescurley@charlescurley.com> - 2024-01-08 00:00 +0100
                Re: systemd-timesyncd Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-08 01:40 +0100
                VAX emulation/simulation (was Re: systemd-timesyncd) The Wanderer <wanderer@fastmail.fm> - 2024-01-08 02:10 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) Bret Busby <bret@busby.net> - 2024-01-08 10:40 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Jeremy Nicoll" <jn.ml.dbi.73@letterboxes.org> - 2024-01-08 11:40 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-08 13:20 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) Nicholas Geovanis <nickgeovanis@gmail.com> - 2024-01-09 01:00 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-09 09:20 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) Bret Busby <bret@busby.net> - 2024-01-09 10:40 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Thomas Schmitt" <scdbackup@gmx.net> - 2024-01-09 11:20 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) Nicolas George <george@nsup.org> - 2024-01-09 11:40 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) gene heskett <gheskett@shentel.net> - 2024-01-09 12:30 +0100
                Re: VAX emulation/simulation (was Re: systemd-timesyncd) "Niall O'Reilly" <niall+lists@no8.be> - 2024-01-08 21:50 +0100
                Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-08 16:00 +0100
                Re: systemd-timesyncd gene heskett <gheskett@shentel.net> - 2024-01-08 16:00 +0100
                Re: systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-08 04:40 +0100
                Re: systemd-timesyncd Curt <curty@free.fr> - 2024-01-08 18:00 +0100
                Re: systemd-timesyncd Max Nikulin <manikulin@gmail.com> - 2024-01-08 04:20 +0100
                Re: systemd-timesyncd Charles Curley <charlescurley@charlescurley.com> - 2024-01-08 05:10 +0100
                Re: systemd-timesyncd Mark Fletcher <mark27q1@gmail.com> - 2024-01-08 14:50 +0100
                mktime (was: Re: systemd and timezone) Max Nikulin <manikulin@gmail.com> - 2023-12-23 18:00 +0100
                Re: mktime (was: Re: systemd and timezone) Jeffrey Walton <noloader@gmail.com> - 2023-12-23 19:30 +0100
                Re: mktime Max Nikulin <manikulin@gmail.com> - 2023-12-24 03:40 +0100
                Re: mktime (was: Re: systemd and timezone) <tomas@tuxteam.de> - 2023-12-24 08:40 +0100
                Re: mktime Max Nikulin <manikulin@gmail.com> - 2023-12-28 03:40 +0100
                Re: systemd and timezone Max Nikulin <manikulin@gmail.com> - 2023-12-21 16:30 +0100
                Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-22 03:20 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-22 08:00 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-21 05:40 +0100
                Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-21 06:50 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-21 07:10 +0100
                Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-21 08:10 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 13:40 +0100
                Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-21 16:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 19:30 +0100
                Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-21 21:00 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 21:10 +0100
                Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-21 21:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-21 22:40 +0100
                Re: difference in seconds between two formatted dates ... gene heskett <gheskett@shentel.net> - 2023-12-22 00:40 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 16:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-25 18:40 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 08:00 +0100
                Re: difference in seconds between two formatted dates ... "Thomas Schmitt" <scdbackup@gmx.net> - 2023-12-26 08:30 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 16:00 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-26 16:40 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-26 19:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-26 22:40 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-27 01:40 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-27 01:50 +0100
                When strace breaks process or is blocked (was: Re: difference in  seconds between two formatted dates ...) Max Nikulin <manikulin@gmail.com> - 2023-12-27 17:50 +0100
            Re: difference in seconds between two formatted dates ... Max Nikulin <manikulin@gmail.com> - 2023-12-18 03:30 +0100
              Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 00:10 +0100
                Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-25 01:10 +0100
                Re: difference in seconds between two formatted dates ... Albretch Mueller <lbrtchx@gmail.com> - 2023-12-25 01:30 +0100
                Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-25 02:20 +0100
                Re: difference in seconds between two formatted dates ... "Andrew M.A. Cater" <amacater@einval.com> - 2023-12-25 11:40 +0100
                Re: difference in seconds between two formatted dates ... Tixy <tixy@yxit.co.uk> - 2023-12-25 09:10 +0100
                Re: difference in seconds between two formatted dates ... Andy Smith <andy@strugglers.net> - 2023-12-27 00:00 +0100
        Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-17 19:00 +0100
        Re: difference in seconds between two formatted dates ... David Wright <deblis@lionunicorn.co.uk> - 2023-12-17 19:30 +0100
    Re: difference in seconds between two formatted dates ... Teemu Likonen <tlikonen@iki.fi> - 2023-12-17 12:50 +0100
  Re: difference in seconds between two formatted dates ... <tomas@tuxteam.de> - 2023-12-17 12:10 +0100
  Re: difference in seconds between two formatted dates ... Greg Wooledge <greg@wooledge.org> - 2023-12-17 15:10 +0100

csiph-web