You could run a master script which scans each of the virtual queues and then activates Mailmanctl for that virtual domain if it has a queued up message. The problem would come in knowing when to stop the daemon.
It's an interesting problem. On Thu, 2003-01-23 at 05:29, Matt Brown wrote: > Is it possible to run Mailman 2.1 from cron, a la v 2.0.13? > > Some background: > I'm running a virtualhosting environment where each host gets it's own > copy of mailman installed. I know that 2.1 can handle virtualhosts, but > the (current) inability to have two lists with the same name under > different domains is a show stopper for me. Each server has 100-200 > domains, and having 7 Mailman processes running for each domain is > excessive, especially considering many of the domains don't actually > have lists running much of the time. I could just stick with 2.0.13 for > now, but I really like the improvements in 2.1. > > Thanks for any advice. > > -- > Matt Brown > > > ------------------------------------------------------ > 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/jonc%40nc.rr.com ------------------------------------------------------ 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
