[Ccd to list for info (and it gets archived)]
paulm@??? said:
} I don't recall ever seeing it specifically mentioned, but, if I
} upgrade from Exim1.82 to 2.02, do I need to do any of the following:
I guess this should go in the README or specific Release Notes - I expect
it would should there be a required upgrade procedure, but this has not
been an issue for quite a while.
} - (probably not) ensure mail spool is flushed beforehand, i.e. queue
} empty
No need to flush mail spool for upgrade from any exim release I can think
of.
} - that I remove the DB files, to ensure a clean startup
No need to remove DB files for upgrade from any exim release I can think
of.
However there was a change in locking procedure for db files a while back,
so if you have a *really* ancient exim (0.x) then you would need to
completely stop exim, upgrade and restart.
Personally I always just upgrade the RPMs (I use a Red Hat based linux
system and package everything into RPM packages) on the systems, whilst it
is running, and then HUP the daemon. This has worked flawlessly for me.
Your milage may vary.... [However I tend to upgrade often and
incrementally, and I do have a spare machine (although with slightly
suspect hardware) to try new versions on for a day before I go live]
Nigel.
--
[ Nigel.Metheringham@??? - Systems Software Engineer ]
[ Tel : +44 113 207 6112 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
--
*** Exim information can be found at
http://www.exim.org/ ***
