On Fri, 2006-03-03 at 03:33 -0500, Lee Revell wrote:
> On Thu, 2006-03-02 at 13:49 -0800, Jim Dennis wrote:
> >
> > I ask primarily because of the interplay between 64-bit systems and
> > things like /var/log/lastlog (which appears as a 1.2TiB file due to
> > the nfsnobody UID of 4294967294).
> >
> > (I'm realize that adding support for these additional seek() flags
> > wouldn't solve the problem ... archiving tools would still have to
> > implement it. And I can also hear the argument that Red Hat and other
> > distributions should re-implement lastlog handling to use a more modern
> > and efficient hashing/index format and perhaps that they should set
> > nfsnobody to "-1" ...
>
> So the presence of very high UIDs causes lastlog to be huge? That just
> sounds like a RedHat bug.
it causes it to be a sparse file
lastlog is an array based file format ;)
but sparse
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
