Joel MARGOT wrote:
[snip]
> Is there a way to upgrade smoothly either reusing the /lists
from
> 1.93 into 1.94.4?
When I took over the lists at a new site and upgraded MD for the first
time, it was (as we say in the technical world :) a mess. I adapted a
system I have used in similar situations with much success. Let's say
that you have your MD stuff set up in /usr/local/majordomo. What I did
was set up a tree like this:
/usr/local/majordomo
/lists
/1.94.4
/current (symlink to ./1.94.4)
I installed the new MD to /1.94.4, tested it, and when I was confident
that it was working properly I created the symlink for /current which
points to the 1.94.4 directory. This was in conjunction with changing my
aliases to this:
majordomo: "|/usr/local/majordomo/current/wrapper majordomo"
The next time I have to upgrade, all I need to do is install the new one
in /usr/local/majordomo/2.0 and when I'm happy with that, I change the
symlink.
Once you've done this and you're happy with the way the new majordomo is
working, you'll want to issue a "newconfig" command for each list to
update its list.config file. It would be really really nice if you could
do this from the command line, but I'm 98% sure that you have to do it
in an e-mail message.
I would be interested in comments regarding this system, especially if
anyone sees a flaw in it. It has been working well for me for over a
month, but I'm still somewhat new to majordomo.
Hope this helps,
Doug
--
*** Chief Operations Officer, DALnet IRC network *** ***
Proud operator, designer and maintainer of the world's largest ***
Internet Relay Chat server. 5,328 clients and still growing. *** Try
spider.dal.net on ports 6662-4 (Powered by FreeBSD)
|
|
