So in this case, I'm not surprised if BerkeleyDB conked out on any
application. I've been burned before, and now I'm, moving away from
BerkeleyDB -- far far away.
funny that sleepycat touts BDB as in use inside the iron of big companies like lucent and cisco.
also remember that mysql uses BDB for one of its table types.
"it ain't libdb, it's what's between the keyboard and the chair" :)
that said, cross-process locking IS tricky business: these guys (lucent, cisco, mysql..) are happy with BDB because they know how to handle this. it could be something as simple as a simple flock() file so that only one of your processes is writing to the BDB file at a time.
but life is short.. better to use MySQL.
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
