In message <[EMAIL PROTECTED]>
so spake Hal DeVore (haldevore):
> The "usual suspect" is locking. There ain't none. Sequences
> seem to be the most susceptible from the postings of problems
> I've seen over the years.
Funny you should mention this -- I implemented sequence file locking
the other day. I still get occasiontal corruption, however. I'm
going to run with this for a while longer and submit a patch. I
also have an alternate version which just uses mkstemp to make the
new sequences file and then rename()s it into place so no process
even has their open sequence file stomped. That may be the better
approach.
- todd
