On Wed, Oct 13, 2010 at 06:16:26PM -0500, Les Mikesell wrote:
On 10/13/2010 6:01 PM, Stephen Harris wrote:
lastlog is a sparse file. How it looks and how big it is are two different things.
And how long it takes to copy if you back the system up is a 3rd thing.
Get better backup software that understands sparse files. You'll have the same problem with dbm files and similar.
But if you've truncated to 32 bits it might be tolerable anyway. On
The bit-size of the OS is irrelevant to the maximum file size. Otherwise we'd still be stuck at 2Gb (maybe 4Gb) files on 32bit systems.
64-bit centos3, nfsnobody made that somewhat awkward, at least in the early versions - it might have been fixed eventually.
People logged in as nfsnobody? That's the only way lastlog should get that entry. Then you have bigger problems...