On Mon, Jul 14, 2008 at 11:33 AM, Mark Sapiro <[EMAIL PROTECTED]> wrote: > > Someone else reported a similar symptom a month or two ago. (I just > tried to find this in the archive, and I see it was you, not someone > else.)
Yes - I reported this during my migration help email. It was me... > I have no idea how this happened. I suspect somehow instead of > mailman.mbox/mailman.mbox being a file, it somehow became a link back > to its parent. If this is the case, even "rm -rf > /var/lib/mailman/archives/mailman.mbox" may not succeed because it may > loop indefinitely, but it's worth a try. > > At worst, you might be able to "mv > /var/lib/mailman/archives/mailman.mbox junk". Then you could create a > new /var/lib/mailman/archives/mailman.mbox directory and empty > /var/lib/mailman/archives/mailman.mbox/mailman.mbox file with the same > ownership and permissions as the good ones. So I think I am simply going to just "rm -rf /var/lib/mailman/archives/private/mailman.mbox/mailman.box" This will retain the first mailman.box directory which is expected to be there and then remove everything beyond that. I will then assume at some point Mailman will attempt to re-generate a mailbox.mbox file in that directory. Do you think this is a bad idea? ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
