I've had to rebuild a couple of list config databases, and toss out a few corrupted pending pickles. We plan to try the synchronous-write option, do backups (!), and maybe even replace the flakey hardware that's been causing the crashes.
You could also change the filesystem where the mailman queue directory is located, so as to remove any asynchronous or delayed writes that are used by the filesystem, above and beyond any mailman SYNC_AFTER_WRITE feature that may or may not be enabled. You could alternatively run on a journaling filesystem, which should also help.
-- Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
