Date: Fri, 16 Sep 2011 20:17:58 +0200 From: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= <lukasz@wasikowski.net> To: Eric <freebsdlists-ports@chillibear.com> Cc: Matthias Andree <matthias.andree@gmx.de>, ports-list freebsd <freebsd-ports@freebsd.org>, lev@FreeBSD.org Subject: Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).) Message-ID: <4E7392D6.4060309@wasikowski.net> In-Reply-To: <CA99352D.219D1%freebsdlists-ports@chillibear.com> References: <CA99352D.219D1%freebsdlists-ports@chillibear.com>
next in thread | previous in thread | raw e-mail | index | archive | help
W dniu 2011-09-16 18:17, Eric pisze: > Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using > AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart. I'm using it for a long time on my personal box and it's not that great. After some updates there is need to prepare the daemon - adjust configuration for example. Automatic restart will do much harm in that case. Another example: update when there's apache and php in new versions, system has also eaccelerator and some pecl's installed. If php was updated before apache, then apache restart via AFTERINSTALL will leave you with not working www server (because eaccelerator and pecl's were not recompiled). Updating ports should never turn off or restart service - thats my $0.02. -- best regards, Lukasz Wasikowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E7392D6.4060309>