On Sat, 30 Oct 2010, Mark Sapiro wrote:
/usr/mailman/lists/[listname]/config.pck.tmp.<hostname>.<pid> file and try moving that to /usr/mailman/lists/[listname]/config.pck if it exists, but even if it does, it may be bad too.
Thanks for the terrible news :-/ Is my [completely off the cuff] understanding of the config file correct that it just holds the settings from the config pages? If so, is there any reason I cannot "create" a new list (after moving the existing one) with the same name and then sub the new config.pck for the old corrupted one?
Thanks for the flush information: even though this was a unique situation (every box in the rack was damaged, several beyond repair [including the backup server]), living in the middle of the tornado capital of the world means it could realistically happen again, so thats a really good one to know.
//Alif
-- "Never belong to any party, always oppose privileged classes and public plunderers, never lack sympathy with the poor, always remain devoted to the public welfare, never be satisfied with merely printing news, always be drastically independent, never be afraid to attack wrong, whether by predatory plutocracy or predatory poverty."
Joseph Pulitzer, 1907 Speech