I simply did a clean install to another directory (majordomo1). Then I
put an alias to the new directory in my aliases file. I set up a new
"sample" list and sent a subscription to majordomo1@wherever.com. Once I
had tested all the commands to the "sample" list.
Then I moved all my
list files over to the /majordomo1/lists/ directory, except for the
subscription lists. I changed the config files by issueing the
"writeconfig" command for each list.config file (anyone have a script
that will go through and update each config file?). I then copied all the
subscription files over to the /majorodomo1/lists/ directory.
Once I was sure everything was working with the "sample" list, I tested a
couple of the other lists and finally, I changed the name of
majordomo1 to majordomo, writing over the old directory. There didn't
seem to be any interruption of service, but then these 25 lists probably
don't get as much traffic as some others.
Christopher Adams
Automated Systems
Oregon State Library
chris@sparkie.osl.state.or.us
On Thu, 22 May 1997, Mats Dufberg wrote:
> Date: Thu, 22 May 97 20:07:50 +0200
> From: Mats Dufberg <Mats.Dufberg@abc.se>
> To: Majordomo Users <majordomo-users@GreatCircle.COM>
> Subject: How to upgrade
>
> I'm about to upgrade from 1.94.1 to 1.94.3. When reading
> the instructions for "clean upgrade" I realized that I
> would either have to kill sendmail or risk getting a
> break in the list service.
>
> How do experienced majordomo upgraders go about?
>
>
>
> Mats Dufberg
> mats.dufberg@abc.se
>
>
>
>
Follow-Ups:
References:
|
|
