public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at cs dot ucla.edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28146] Migrate utmp/utmpx API to time64
Date: Mon, 07 Aug 2023 19:11:33 +0000 [thread overview]
Message-ID: <bug-28146-131-7OrW2fDsrd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28146-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28146
eggert at cs dot ucla.edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eggert at cs dot ucla.edu
--- Comment #1 from eggert at cs dot ucla.edu ---
Also see related glibc bug 30701 - which affects applications today if they're
compiled with 'gcc -m32 -D_TIME_BITS=64' - along with the following coreutils
bug report:
https://bugs.gnu.org/64937
which discusses how this utmp/wtmp problem afflicts apps like 'who', 'last',
'lastb', 'sessreg', and GNU Emacs.
The coreutils bug report suggests there is some sentiment for dumping
utmp/wtmp/btmp and going to a daemon-based system. If that's done, there needs
to be plenty of time for a changeover. As things stand, today's 64-bit apps
will stop working on x86-64 in the year 2038, they'll need time to adapt to a
daemon-based system, and the solution needs to be stable well before the year
2038 rolls around.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-08-07 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 11:11 [Bug libc/28146] New: " schwab@linux-m68k.org
2023-07-31 9:49 ` [Bug libc/28146] " sam at gentoo dot org
2023-08-07 19:11 ` eggert at cs dot ucla.edu [this message]
2023-08-07 20:07 ` sam at gentoo dot org
2024-04-09 6:56 ` fweimer at redhat dot com
2024-04-09 6:58 ` fweimer at redhat dot com
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=bug-28146-131-7OrW2fDsrd@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).