Re: How best to handle upgrade of Cyrus spool?
Michael-John Turner <mj@turner.org.za> wrote:
> Cyrus 2.x requires a new spool dir hierarchy and a script exists to migrate
> from earlier releases (this would be run from postinst). The problem is
> that the the user's MTA needs to be shut down _before_ this migration
> process starts, otherwise a situation could exist where the MTA runs the
> new 2.x delivery agent but the directories are still in the old 1.x
> layout, causing all sorts of nastiness.
Make the delivering agent fail with EX_TEMPFAIL if /var/lock/cyrus-nodeliver
exists. Then create that file in preinst and remove it after you've
finished the conversion in postinst.
You might want to make the delivering agent hang instead of returning with
EX_TEMPFAIL if there are MTAs out there that don't deal with this correctly.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Reply to: