3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] gdbmopen
FromSent OnAttachments
Henk van LingenApr 11, 2005 7:17 am 
Matthias AndreeApr 11, 2005 7:40 am 
Sam VarshavchikApr 11, 2005 2:56 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] gdbmopenActions...
From:Matthias Andree (ma+c@dt.e-technik.uni-dortmund.de)
Date:Apr 11, 2005 7:40:39 am
List:net.sourceforge.lists.courier-maildrop

Henk van Lingen <hen@cs.uu.nl> writes:

The gdbmopen docs says:

"The GDBM library allows multiple processes to read the same GDBM file at the same time, but it does not allow multiple access when the GDBM file is open for writing. "

Does that mean that 'gdbmopen(".vacation.dat", "C")' will fail when it is already open or will it open the file anyway and will a following 'gdbmstore()' fail?

I haven't looked at the code, a sane approach would be to block readers while a writer is active and vice versa, and perhaps time out the lock after a few minutes causing EX_TEMPFAIL or similar.

-- Matthias Andree