The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Michael Kjörling" <michael@kjorling.se>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Happy birthday, Unix timestamp!
Date: Fri, 9 Sep 2022 07:03:10 +0000	[thread overview]
Message-ID: <392d6229-63e5-42ca-87be-dc83e78e4172@home.arpa> (raw)
In-Reply-To: <22fb8110-9d31-4025-a4ab-73eb643a99d1@www.fastmail.com>

On 8 Sep 2022 20:29 -0700, from web@loomcom.com (Seth Morabito):
> Well, you can imagine what happened when the leading digit changed
> from an ASCII "9" to an ASCII "1". Oops.

Let me guess. Something very similar to what happened to Microsoft
Exchange servers when the first two digits in a 32-bit signed integer
representation of the current date and time (formatted as YYMMDDHHMM)
changed from "21" to "22" as the date became January 1, 2022.

For those who don't immediately realize why that's a snafu: what is
the value of (2^31)-1 when interpreted as a string representation of a
timestamp according to that format, and how does that relate to Jan 1
2022?

-- 
Michael Kjörling • https://michael.kjorling.se • michael@kjorling.se
 “Remember when, on the Internet, nobody cared that you were a dog?”


  reply	other threads:[~2022-09-09  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 22:28 [TUHS] " Dave Horsfall
2022-09-08 23:48 ` [TUHS] " Rob Pike
2022-09-09  0:11   ` Dan Cross
2022-09-09  4:24   ` Rob Pike
2022-09-11  0:09   ` Dave Horsfall
2022-09-09  3:29 ` Seth Morabito
2022-09-09  7:03   ` Michael Kjörling [this message]
2022-09-09 12:06 Douglas McIlroy
2022-09-09 17:16 ` Andrew Hume
2022-09-09 18:53 Norman Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=392d6229-63e5-42ca-87be-dc83e78e4172@home.arpa \
    --to=michael@kjorling.se \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).