Doh! Yep. Sharing the Lock file directory would work fine for Mailman version 2.0.13, but not for 2.1.x... Sorry for the bad advice.
Your best bet for 2.1.x is to run the servers with local list files and let a background process keep the lists up-to-date or synchronized. You could simply have all mail for <listname-request> forwarded to a primary server, and have the web access be to that primary server as well. That primary server would then run a process that propagated any list changes to the slave servers. Good luck - and sorry for the wrong turn. Jon Carnes On Mon, 2003-10-27 at 07:41, javier wrote: > Ok! jonh, when i try to start second mailmanctl i got ab error, but i > got to start second mailmanctl with -s flag.... but i don't know wath > i'm doing,.... > so... Somebody knows if this is good?? > > bash-2.03# ./mailmanctl start > The master qrunner lock could not be acquired, because it appears as if some > process on some other host may have acquired it. We can't test for stale > locks across host boundaries, so you'll have to do this manually. Or, > if you > know the lock is stale, re-run mailmanctl with the -s flag. > > Lock file: /usr/local/mailman/locks/master-qrunner > Lock host: burlador > > Exiting. > bash-2.03# ./mailmanctl -s start > Starting Mailman's master qrunner. ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
