Date: Mon, 31 Oct 2011 11:54:04 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-ports@freebsd.org Subject: Re: ports/162049: The Ports tree lacks a framework to restart services Message-ID: <4EAE8C5C.5020409@infracaninophile.co.uk> In-Reply-To: <4EAE7B59.7010104@bsdforen.de> References: <20111027091500.GM63910@hoeg.nl> <20111027162715.GB1012@sysmon.tcworks.net> <4EAE401B.2040704@FreeBSD.org> <4EAE5075.6030102@bsdforen.de> <4EAE5E2D.3060209@FreeBSD.org> <4EAE7B59.7010104@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig7EFF2425E76924C0C68E7C9B
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
On 31/10/2011 10:41, Dominic Fandrey wrote:
> I just wanted to hint that such a function is already in place and I do=
n't
> think it would be difficult to add the possibility to start a service.
Restarting a single service is no big deal. Trouble is there are a lot
of cases where that just isn't the right thing to do. Suppose you have
a very common situation: a web application written in PHP and using a RDB=
MS.
* Upgrades to the RDBMS often require more than just a restart of the
DB. Eg. changes to internal schemas require running some external
script. (pg_upgrade, mysql_after_upgrade, etc.)
* Upgrades to PHP -- given that PHP is modularized, then the sane
way of restarting is to take the web app down at the point
lang/php5 gets reinstalled, but not bring it up again until all
the various php5 modules have been reinstalled. At minimum. If
you use, say, eAccelerator, then you almost certainly need to
rebuild that before restarting the php web-app.
* Of course, how to restart a PHP based web-app is highly context
dependent. Generally it means bouncing some other daemon:
frequently a web server like apache, or is it lighttpd? Or some
sort of FCGI daemon?
* Certainly no one would ever write a DB based web-app that wouldn't
cope gracefully with the temporary disappearance of its back-end
DB. Why, such a thing would be clearly beyond the bounds of
possibility, and it would be vanishingly improbable that
anyone should ever need to worry about needing to restart a
web-app as a consequence of restarting a DB.
Basically, I think I can summarize by saying that as soon as you go
beyond the simplest and most basic system configurations, there are so
many different possibilities that it requires some sort of intelligent
agent to manage the upgrade and restart process. Failing the widespread
availability of practicable AI, this is where your sysadmins are going
to earn their princely salaries.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
--------------enig7EFF2425E76924C0C68E7C9B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk6ujGUACgkQ8Mjk52CukIwjnACfVFByd6SIaRf1qKzl7pDTl1qN
TDwAni9l07xcbULFA0r3JIhqSBIlQ4eT
=FhiM
-----END PGP SIGNATURE-----
--------------enig7EFF2425E76924C0C68E7C9B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EAE8C5C.5020409>