LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Stan Horwitz <[log in to unmask]>
Thu, 16 Nov 2006 11:31:03 -0500
text/plain (40 lines)
On Nov 16, 2006, at 11:26 AM — 11/16/06, Stacey Conrad wrote:

> Hello all,
>
> Next week we'll be moving our Listserv installation to a new box.  The
> old is 1.8e running on Solaris 8, and the new is 14.5 on Solaris  
> 10.  I
> have read the "Moving Listserv to a New Server" document and noticed
> that it says to upgrade the Listserv installation on the old box, THEN
> move data to the new box.  We'd like to keep the old box as-is, in  
> case
> we need to fall back on it.
>
> So the first question I have is this: is it possible to do the move
> without upgrading the original box first, or is that a bad idea?

Sure, its possible. The only reason to do the software upgrade before  
the server migration is
to allow you to isolate any problems that might occur that are caused  
by the server migration or
the software upgrade. If you do both at the same time, isolating any  
problems might be a
challenge; however, if you do the upgrade properly, you are unlikely  
to have any problems.

> My second question is regarding aliases for the lists (running
> sendmail).  I noticed the aliases are different on the new version,  
> and
> I don't see a way to update them.  We have way too many lists to
> consider re-creating aliases individually.  Does upgrading the  
> original
> install take care up updating the aliases, or is there a way to do a
> bulk creation of aliases?
>
> I've done some testing with a test list and everything -appears- to  
> work
> ok, but I just wanted to check with the list to make sure everything
> will go smoothly.

Why not just write a shell script to make the transition in alias files?

ATOM RSS1 RSS2