On Thu, 2002-11-21 at 03:42, Ian Chilton wrote: > ok, i'll rsync them across every 1/2hr or so and hope that the main > server is not unavailable for the time before someone changing a > subscription and the next rsync :)
Create a file in the locking directory: qrunner.lock.moya.trilug.org.22845 That should lock out qrunner from accessing the lists while you do your sync. Be sure to delete the lock file when your sync is done. > > Are there any mailman developers around here? - a much better solution > would be to turn on a "backup server" option in the config file, > specifying the e-mail address of the list server on the backup server. > What should then happen if this is on, is whenever a list is changed > either with mail commands or the web interface, it should send a mail to > the backup server to make these same changes. This sounds very easy to > implement but would be very useful! Mailman's logs are a rich resource for information on users subscriptions and unsubscriptions. You could easily setup some scripts to populate the changes from one installation onto another one. Of course that doesn't handle list configuration changes, but a simple config_list dump could easily propagate those settings. Good Luck - Jon Carnes ------------------------------------------------------ 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
