diff options
| author | peter <peter@FreeBSD.org> | 1995-12-11 13:56:07 +0000 |
|---|---|---|
| committer | peter <peter@FreeBSD.org> | 1995-12-11 13:56:07 +0000 |
| commit | d20b5a1c02ba491671cfa7ff58c322ea8affb8b8 (patch) | |
| tree | 4ebd51351fa8df00e3fe7d980b0624d2f67f82eb /usr.bin/lastcomm/lastcomm.1 | |
| parent | 286d95551f8211bbe15b8be12c6eaf9325c1232f (diff) | |
| download | FreeBSD-src-d20b5a1c02ba491671cfa7ff58c322ea8affb8b8.zip FreeBSD-src-d20b5a1c02ba491671cfa7ff58c322ea8affb8b8.tar.gz | |
Fix yp_mkdb to do what the code suggests it's trying to do..
The code, as written, appears to load the new database data into a new
hash file and renames the two.
Due to a run of bugs and lack of error checking, it's going a whole
mess of unlink() and rename() calls that are failing. It only
worked in the first place because the data was being inserted into a
"live" hash file. (I wonder how much stale data has assumulated?)
Submitted by: Laurence Lopez <lopez@mv.mv.com>
Diffstat (limited to 'usr.bin/lastcomm/lastcomm.1')
0 files changed, 0 insertions, 0 deletions
