Quoting Alan Brown ([EMAIL PROTECTED]): > On Fri, 11 Jul 2003, Brad Stockdale wrote: > > > -ERR [SYS/TEMP] Unable to open Bulletin database; contact your > > administrator > > > > gdbm_open failed: Resource temporarily unavailable (11) > > This happens when 2 clients access the BullDB simultaneously. > > > What can cause this type of problem? More appropriately, what would be > > a good fix for it? > > There isn't a good fix, unfortunately. The DB needs to be opened > read/write in order to mark the last-read bulletin for each user as the > pull down messages. > > Doubtless you'll find that the message happens more often after you > update a bulletin. I did.
This would suggest that it's being kept open for a while. With some DBs (berkeley/sleepycat DB 3.x and 4.x) I should be able to use transactions and/or lock+open, write, close very quickly. I know that, for example, sendmail will have many processes writing to the statistics file, but it's done very very quickly and let go, so concurrent access isn't such a notable problem. Can the qpopper code be optimized? Can GNU DBM be replaced with a better database? > The only workaround is to not use Bulletin databases, but that leaves > files in user directrories which some may erase.
