[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: db(3) removal and lastlogx
On Thu, Jun 07, 2012 at 09:25:41AM +0200, Joerg Sonnenberger wrote:
> > >(1) Just use a sparse file. This requires by far the least amount
> > >of code, just some verification logic for a file header and
> > >writing to "uid * size of entry". Writes should be short enough to
> > >ensure atomic writes even on NFS. Same for reads. No manual
> > >locking needed.
Historically, the lastlog file has always been exactly this. I see no
reason to do anything else.
> I don't really consider this an option either. Especially for a file
> where updates happen all the time and e.g. the crash reliability of
> db(3) is a real concern.
The lastlog file isn't exactly mission-critical data.
David A. Holland
Main Index |
Thread Index |