> [ ... ]After the 2.8.10 release ... "This version fixes a critical locking bug in Unix. It turns out that any call to close() clears all locks on file that was closed (who knew?) which then left the database vulnerable to corruption from other processes. That bug has been cleared by embargoing all close() calls until all locks of been released."
I have made some investigation...
From "Advanced Programming in the UNIX Environment" by R. Stevens:
Hi Marco,
thank you for this clarification. But what does R. Stevens write about how to circumvent this strange behaviour?
/eno
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
