Date: Tue, 27 Jun 2017 19:32:47 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Matthias Fechner <idefix@fechner.net>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: Should a package restart on upgrade itself Message-ID: <595296BF.3040906@quip.cz> In-Reply-To: <b71469f3-dd9d-6680-f85e-a7acfcf9d944@fechner.net> References: <b71469f3-dd9d-6680-f85e-a7acfcf9d944@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Fechner wrote on 2017/06/27 18:29: > Dear all, > > it is always a pain if pkg upgrade a lot of packages to restart all > services to make sure update/security fixes are applied to all running > services. > > Is there an option in pkg that it restart services automatically or is > it OK if I would add a post-install script to the packages (I maintain) > that will include a "service foo restart"? > > What is best practice here? Please don't do this. Some ports did this in the past and this was really a pain during larger upgrades. It sometimes leave services stopped (hi MySQL). The same bad practice is disabling / enabling Apache modules on upgrade. pkg upgrade should just do it's work - upgrade packages on disk. But manipulating config files and restart of services is up to me - the Administrator (or my tools). It would be nice to have some kind of "hooks" in pkg, which can be used to notify deployment tools that some services should be (re)started, or do restart in some simpler environment if user allows this (setup hooks for service restart). But is must not be done automatically for individual ports / packages even if maintainer thinks it is Good Idea (tm) Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?595296BF.3040906>