Date: Sun, 25 Feb 1996 17:12:37 -0800 From: Paul Traina <pst@shockwave.com> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-current@freebsd.org, jhay@mikom.csir.co.za Subject: Re: Bug in libc/db/hash/hash.c??? Message-ID: <199602260112.RAA04186@precipice.shockwave.com> In-Reply-To: Your message of "Mon, 26 Feb 1996 06:54:00 %2B1100." <199602251954.GAA32445@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Bruce Evans <bde@zeta.org.au> Subject: Re: Bug in libc/db/hash/hash.c??? > I think the fix works because the O_CREAT flag is now honoured (perhaps > it should check O_TRUNC too?). I think the database was messed up when > cgetnext() opened it without (O_CREAT | O_TRUNC). >Do you mean it should require both O_CREAT and O_TRUNC or either? If either >>, >that case is covered earlier. I'm not certain both should be required if >the file is already 0 sized. However, I'm easy going, whichever you want >is fine by me, just as long as you clarify what you want. :-) I think backing it out was best :-). 0-length database files shouldn't exist unless another process is initializing them, and you can't fix a 0-length `cap' database file except by deleting it. The whole point was that mh's slocal uses an 0-length file to indicate that it should keep track of message id's, that's the only way to bootstrap yourself up.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602260112.RAA04186>