public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.com>
To: libc-alpha@sourceware.org
Subject: Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32
Date: Tue, 14 Feb 2023 09:24:09 +0100	[thread overview]
Message-ID: <20230214082409.GA29974@suse.com> (raw)
In-Reply-To: <901005ca-640f-3a8f-a199-c1374f3cf141@linaro.org>

On Wed, Feb 08, Adhemerval Zanella Netto via Libc-alpha wrote:

> I proposed a fix for the utmp/utmpx/lastlog interface on the initial 64 bit
> time_t support [1] (patch 16 to 22) and Florian suggested to just deprecate
> the interface altogether (the DoS BZ#24492 essentially requires rewrite to
> use an external daemon, which is not what we want).
> 
> My proposal was essentially to create new path and use 64-bit time_t field,
> along with some internal conversions if the old path is used.  I ended drop
> this part from 64 bit interface because it is a legacy interface and it 
> would most likely generate some breakage.

Thanks for this informations.

I agree that utmp/wtmp are legacy and started to collect data, which
applications uses utmp/wtmp/btmp/lastlog on a typical openSUSE server
installation:

https://github.com/thkukuk/utmpx/blob/main/Y2038.md

The biggest problem is, there are still quite some tools which modifies
utmp/wtmp directly, so that code needs to be rewriten anyways.

I think we don't lose anything if btmp and lastlog don't exist anymore.
Querying utmp for the runlevel in systemd times is also obsolete.
Statistical data how many users are logged in if you login or if you
call uptime is also only nice to have, nothing more.

So the main consumer of utmp is glibc itself: getlogin()/getlogin_r()
Is there any idea how to replace that, if utmp/wtmp gets deprecated?
That's the only use case for which I don't see an alternate currently.
The musl libc way to use an environment variable is really not safe...

Another real usecase is to find the TTYs for wall and wall alike
messages by tools like shutdown, systemd and similar.

Functions like login()/logout() are only used by openssh. So should be
solveable, too.

  Thorsten


> 
> [1] https://sourceware.org/pipermail/libc-alpha/2021-March/123341.html

-- 
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany
Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)

  reply	other threads:[~2023-02-14  8:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  9:18 Thorsten Kukuk
2023-02-08 10:06 ` Andreas Schwab
     [not found] ` <0869a6f98f29405eb431f63db593c490@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:11   ` Thorsten Kukuk
2023-02-08 10:17     ` Andreas Schwab
     [not found]     ` <d2f1ee273add4af0868e07dc32542687@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:22       ` Thorsten Kukuk
2023-02-08 10:27         ` Andreas Schwab
     [not found]         ` <7485b79473614eaa994d3ea79c91629a@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:38           ` Thorsten Kukuk
2023-02-08 11:48             ` Adhemerval Zanella Netto
2023-02-14  8:24               ` Thorsten Kukuk [this message]
2023-02-14  8:59                 ` Florian Weimer
     [not found]                 ` <3230d2f8fa214c268cba52e699c14ae2@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-14  9:26                   ` Thorsten Kukuk
2023-02-14 14:28                     ` Adhemerval Zanella Netto
2023-02-16 13:59                   ` Thorsten Kukuk
2023-04-11 11:40                     ` Thorsten Kukuk
2023-04-11 13:23                       ` Adhemerval Zanella Netto
2023-09-25  7:30                         ` Thorsten Kukuk
2023-04-11 21:41                       ` Paul Eggert
2023-04-12  6:55                         ` Thorsten Kukuk
2023-04-12 23:36                           ` Paul Eggert

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=20230214082409.GA29974@suse.com \
    --to=kukuk@suse.com \
    --cc=libc-alpha@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).