[Pkg-shadow-devel] Re: (forw) Bug#280212: lastlog: fails when high UIDs are present

Tomasz Kłoczko kloczek@zie.pg.gda.pl
Thu, 6 Jan 2005 18:23:07 +0100 (CET)

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

Content-Type: TEXT/PLAIN; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Thu, 6 Jan 2005, Christian Perrier wrote:
> Attention was drawn to this bug on IRC today.  Since using a 32-bit index
> for a file that has more than one byte of data per entry makes it very
> possible to have files that exceed a 32-bit file size limit, I agree that
> this is a bug and should be fixed.
> Two caveats, however:
> - it is not safe to use the 64-bit flags in a program if it also exchange=
>  file-related structs with a library that does not have 64-bit support
>  enabled (I don't think this is a problem here)
> - the 64-bit flags don't necessarily have the expected effect on platform=
>  that are natively 64-bit -- c.f. bug #280213 (hmm, what a coincidental b=
>  #) on exim.  The safe way to do this seems to be to use the output of
>  "getconf LFS_CFLAGS".

From=20current shadow CVS tree NEWS file:

shadow-4.0.6 -> shadow-4.0.7

- fixed large file support in lastlog and faillog:
-- added AC_SYS_LARGEFILE macro to autoconf,
-- use fseeko() instead fseek() and remove casting file ofsets to unsigned

So upcomming shadow 4.0.7 will be LFS compliant :^)

*Ludzie nie maj=B1 problem=F3w, tylko sobie sami je stwarzaj=B1*
Tomasz K=B3oczko, sys adm @zie.pg.gda.pl|*e-mail: kloczek@rudy.mif.pg.gda.p=