I'm pursuing a bug in nntpcache (version 2.3.3+patches from this list) and I've located the problem in a mmap file corruption. In particular, mmalloc failure to unlink a free block assigned, since "prev" and "next" pointers are "corrupted". Digging into the source code, I can't see any mecanish to arbitrate mmap access (using mmalloc()/mfree()) between nntpcache processes. Am I missing anything? PS: I've studied nntpcache code only for 3-4 hours. I'm probably missing the point... -- Jesus Cea Avion _/_/ _/_/_/ _/_/_/ jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ _/_/_/_/_/ PGP Key Available at KeyServ _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz
