> Looking into, we found that in upas/common/libsys.c the > function generating the lock file name returns always "L.mbox" > but not .../L.<mbox file name> as it seems it should.
i think the comment above the function is important "we use one lock per directory". it's been a long time since i worked on nupas, so i don't recall all the details, but iirc, imap4d relies on having one lock per directory. of course, nupas takes pressure off the directory lock by using mdir format, which doesn't require a lock. the indicies are lock files themselves. under what circumstaces did you find a problem? - erik
