From owner-freebsd-questions@FreeBSD.ORG Tue Jul 15 13:33:13 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5AF737B401 for ; Tue, 15 Jul 2003 13:33:13 -0700 (PDT) Received: from mailout.informatik.tu-muenchen.de (mailout.informatik.tu-muenchen.de [131.159.0.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9B9843FBD for ; Tue, 15 Jul 2003 13:33:12 -0700 (PDT) (envelope-from barner@in.tum.de) Received: by zi025.glhnet.mhn.de (Postfix, from userid 1000) id F1A3F386F9; Tue, 15 Jul 2003 22:33:10 +0200 (CEST) Date: Tue, 15 Jul 2003 22:33:10 +0200 From: Simon Barner To: Alfonso Romero Message-ID: <20030715203310.GA14770@zi025.glhnet.mhn.de> References: <006501c3499a$8ac71540$0100a8c0@ibacsoft.dynu.com> <20030714004401.GB537@zi025.glhnet.mhn.de> <00e301c34b03$a17cc680$0100a8c0@ibacsoft.dynu.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <00e301c34b03$a17cc680$0100a8c0@ibacsoft.dynu.com> User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: freebsd-questions Subject: Re: postfix freebsd port with vda patch X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2003 20:33:14 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Alfonso, please avoid top-postings - thanks. > > You can easyly do it yourself. CVSup your ports collection to get the > > latest postfix port, then run 'make patch' and select the desired > > options (sasl, ...). [...] > Thanks for your advice, it worked without any problems. >=20 > I tested it on a spare FreeBSD server. Now I want to update and patch > postfix on my production server. Is there a way I could do that without > having to shut off my production server for too much time? Depending on whether you have the ports collection on your production server, you can do the following: - build postfix with the vda patch as in the previous mail. - ensure you have sysutils/portupgrade on your system - stop the postfix system - portupgrade --noclean postfix_ - start the postfix mail system The port will take care not to overwrite the modfied configuration files, but could can back them up if you want to be extra safe. The other possibility is to build a package on your spare machine, copy it to your server and use pkg_update(1) for the installation. Disclaimer: I have never done this, I don't now what will happen with your configuration files. Another point is whether you want to update the dependencies of postfix to their latest versions - this might also break something, but if you have done your tests with the desired configuration, and everything worked as exspected, there shouldn't be any problem. You can use 'portupgrade -Rn postfix_<...>' to find out which ports need to= be upgraded. Depending on that information you should back up the according data and configuration files. Now you can use 'portupgrade -R -x "postfix_<...>" to update postfix's dependencies (without touching postfix itself). You should be able to do that before stopping the postfix server - but I don't know the exact setup of your mail system, but I hope this mail gave you an idea what to take care of. Regards, Simon --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/FGUGCkn+/eutqCoRApBeAJ9Pfqv3EqFnz21D3a7Tay5eWuiTKgCeNBHq 7U5p/OHf/hwQ9WljflnX+s0= =ziWh -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl--