Question on liblockfile (Re: policy Q's WRT imapd)
On 26 Jan 1998, Rob Browning wrote:
> "Jaldhar H. Vyas" <jaldhar@braincells.com> writes:
> > 1. Is the use of liblockfile mandatory or just A Good Thing? (or a bad
> > thing?)
> > imapd has its own locking scheme which it shares with pine but no other
> > apps afaik. Is that ok or shall I patch it to use liblockfile?
> I'm in favor of always using liblockfile. That way, if something
> changes, and we need to modify our locking strategy, only one package
> needs to be updated to fix all the programs handling mailboxes.
Yes, but is liblockfile relevant to MTAs and MUAs or also to any program
that needs to lock a file? I'm having doubts about whether I can use it
locking shared data files in addressbook package, since it seems to
geared towards stuff from /var/spool/mail. After all, the only
documented function in that library is maillock(3).
So does anyone know if it's safe/kosher/policy-compliant to use
maillock() for non-mail locking?
.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>
Reply to: