I had some similar questions in my upgrade from 1.92 to 1.94.1. I
approached it as a new installation, making a 1.94 directory so that I
could try it out as my lists continued to run under 1.92. My big question
now is- it seems to make sense that I would create new config files for
the lists under 1.94.1, but what about the current config files? Am I
faced with having to complete new config files for all (100+) lists?
Obviously, I lose some functionality using the old config files with the
updated version. Will the old config files work with the new version?
So, I have a the 1.94.1 in a new directory called mdom2. In my aliases, I
added an entry that says mdom2:"|/path/to/mdom2/wrapper majordomo". Now I
can actually create new lists to test before I change over to the new
version. Eventually, I will have all the lists tested with new config
files and then switch over. Does this seem like a good way to approach
it? Any suggestions?
>Subject: Upgrading from 1.93 to 1.94.1
>Sent: 2/12/1997 3:54 AM
>Received: 2/11/1997 9:21 AM
>From: Tabor J. Wells, email@example.com
>Due to a recent onslaught of forged subscription bombs, I'll be upgrading
>our version of Majordomo from 1.93 to 1.94.1 this Sunday. However, before
>I do so, I want to ask about the effects of upgrading "in place" over
>I have a large number of lists (approx 250) which I need to convert, and I
>realize the necessity of doing the writeconfig, but my question is will I
>lose any major functionality if I upgrade & use the old config files for a
>Majordomo currently resides on one of our major mail servers, and I'd
>really rather not have it refusing SMTP connections for a long period of
>Any suggestions or pitfalls to avoid?
>Thanks in advance,
>Tabor J. Wells firstname.lastname@example.org
>UNIX Systems Administrator Just another victim of the ambient morality