If you actually have individual databases driving each install (as opposed to a shared database via NFS or some other tool), then you could easily setup some scripts to keep the databases in sync. You could use the log files as your trigger, or even simple periodic diffs of each individual database.
It would take a couple of hours to write a set of scripts that did it generically, but then you would set! Good Luck - Jon Carnes On Wed, 2002-11-20 at 04:07, Ian Chilton wrote: > Hello, > > > There are several ways to set this up. Here are two examples that I've > > done: > > Thanks for the reply. However this doesn't really answer my origional > question - how do you keep the subscription information in sync across > the multiple servers? > > > Thanks! > > > Bye for Now, > > Ian > > > \|||/ > (o o) > /---------------------------ooO-(_)-Ooo---------------------------\ > | Ian Chilton Web: http://www.ichilton.co.uk | > | E-Mail: [EMAIL PROTECTED] Backup: [EMAIL PROTECTED] | > |-----------------------------------------------------------------| > | There are 10 types of people in the world: | > | Those who understand binary, and those who don't. | > \-----------------------------------------------------------------/ > ------------------------------------------------------ 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
