Re: db(3) removal and lastlogx

[yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi)]

hi,

> Considering lastlogx, it seems like the db(3) use provides an
> interesting DOS vector. If I run login and SIGSTOP it after it opened
> the file with exclusive log, but before it finished writting the entry,
> it should provide other instances from doing the same. In other words,
> we really want to have a file format that works without any exclusive
> lock on the (database) file.

does your proprosed format work without locks?

YAMAMOTO Takashi