There isn't any locking of the DBM file in SessDBM. I was operating
under the assumption that this would only be a problem if you were
running mulitple accounting processes, but on some reflection it's
even a problem in my environment where I have 1 auth and 1 acct
process running, since the auth process can write into the DBM to delete
ghost sessions.
I'm uning gdbm, which is multiple-reader, single writer safe. I don't
know what the status of the other dbm implementations are.
--
Aaron Nabil
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
