public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28146] New: Migrate utmp/utmpx API to time64 Date: Tue, 27 Jul 2021 11:11:49 +0000 [thread overview] Message-ID: <bug-28146-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28146 Bug ID: 28146 Summary: Migrate utmp/utmpx API to time64 Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: schwab@linux-m68k.org CC: drepper.fsp at gmail dot com Target Milestone: --- Platforms that define __WORDSIZE_TIME64_COMPAT32 use a 32-bit time stamp in the utmp/utmpx API and the utmp/wtmp files to keep compatibility with 32-bit applications. There needs to be a way forward so that login accounting continues to work beyond the 2038 flag day. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-07-27 11:11 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-27 11:11 schwab@linux-m68k.org [this message] 2023-07-31 9:49 ` [Bug libc/28146] " sam at gentoo dot org 2023-08-07 19:11 ` eggert at cs dot ucla.edu 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@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: linkBe 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).