[Dovecot] Just verifying upgrade procedure?
When upgrading from source, it's ok to just run make install and every files will be overwritten with the new version? Nothing else one should do?
Regards,
BTJ
--
Bjørn T Johansen
btj@havleik.no
Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows"
Bjørn T Johansen a écrit :
When upgrading from source, it's ok to just run make install and every files will be overwritten with the new version? Nothing else one should do?
Pay attention to the fact that the dovecot daemon dynamically starts the imap and pop server executables whenever inboud connexions are requested.
If you upgrade without stopping the master dovecot, and clients request connexions, dovecot will try to run the new imap and pop executables, which are not the same version as the master, and problems may arise.
The "good" solution is to stop the master dovecot *before* make install, and restart it afterwards; or to make sure no clients try to connect before you completed the upgrade process.
-- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.
On Wed, 12 Dec 2007 13:38:48 +0100 Benoit Branciard Benoit.Branciard@univ-paris1.fr wrote:
Bjørn T Johansen a écrit :
When upgrading from source, it's ok to just run make install and every files will be overwritten with the new version? Nothing else one should do?
Pay attention to the fact that the dovecot daemon dynamically starts the imap and pop server executables whenever inboud connexions are requested.
If you upgrade without stopping the master dovecot, and clients request connexions, dovecot will try to run the new imap and pop executables, which are not the same version as the master, and problems may arise.
The "good" solution is to stop the master dovecot *before* make install, and restart it afterwards; or to make sure no clients try to connect before you completed the upgrade process.
Yes, I always stop dovecot before running make install.... :)
BTJ
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
My work plan:
Backup Confs Stop Dovecot I use paco0 to remove all the files from a previous installation: paco -r dovecot I use paco to install the new version paco -lD make install Start Dovecot
and everything are ok (every time !!!)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHYvKlWIK+Pe9twhoRAivGAJ90Xhsui14+hWcF97y7MCYoz3ljEQCfaywR 3EvZfEu8xOEyLtZc1AQu4wg= =oS1L -----END PGP SIGNATURE-----
participants (3)
-
Benoit Branciard
-
Bjørn T Johansen
-
Evaggelos Balaskas