static sqlite makes the library way too big about lastlog2

[thkukuk]

is there any way i can use lastlog2 while keeping the size down?

Only if somebody comes up with support for another database, which is very robust, stable, well maintained, fits with the licenses, etc.
I haven't found an alternative and thus I have no plans to add support for other databases.

[i3roly]

How does the original lastlog achieve this? And what about utmpx or whatever? Same conundrum? bless, g From: Thorsten Kukuk Sent: Tuesday, 9 May 2023 11:59 PM To: thkukuk/lastlog2 Reply To: thkukuk/lastlog2 Cc: gagan sidhu; Author Subject: Re: [thkukuk/lastlog2] static sqlite makes the library way too big (Issue #5) is there any way i can use lastlog2 while keeping the size down? Only if somebody comes up with support for another database, which is very robust, stable, well maintained, fits with the licenses, etc. I haven't found an alternative and thus I have no plans to add support for other databases. — Reply to this email directly, view it on GitHub<#5 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AITLEG6XM2TPOWFC6HB4GN3XFMVEVANCNFSM6AAAAAAX32XW5U>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[thkukuk]

How does the original lastlog achieve this?

sparse files and direct seek access, which is one of the problems why this is not fixable for Y2038.

And what about utmpx or whatever? Same conundrum?

With glibc: utmp = utmpx
With other libc implementations: I don't know.
But: utmp/utmpx have nothing to do with lastlog. Two complete different things with different use cases and requirements.

[i3roly]

thanks thorsten, i guess i'll just have to use regular lastlog for now.