Date: Sun, 11 Dec 2011 09:59:58 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-ports@freebsd.org Subject: Re: again, ports that stop daemons Message-ID: <4EE47F1E.9020104@infracaninophile.co.uk> In-Reply-To: <20111211071947.GA57995@DataIX.net> References: <4ED8C0F1.807@FreeBSD.org> <CAJ_iqta0OCB8SktnR4fXawvEGiGx92wEgtaowMp1U2ooHiMa7Q@mail.gmail.com> <20111202195555.GD1913@azathoth.lan> <4ED95A95.9040805@FreeBSD.org> <20111209211848.GF59666@azathoth.lan> <4EE27CC5.4010006@FreeBSD.org> <20111211071947.GA57995@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2B523ACB452093961C857935 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/12/2011 07:19, Jason Hellenthal wrote: > If end-user is upgrading a package they should be prepared to take > any neccesary action to start the services again after final actions > are complete. Desperate services could have a periodic script that > could handle the checks for these services and I strongly advise > against taking any action whatsoever on starting or restarting or > reloading. Like this? http://www.infracaninophile.co.uk/articles/hotchpotch.html#status-rc Not that I entirely disagree with having a mechanism available to restart daemons on update, but yes, it should definitely be optional and configurable and the docco should explain very clearly that *it will not work properly in all cases*. There are too many corner cases where you've got to worry about the order in which services are restarted, plus things like needing to restart a completely different service when certain ports get upgraded. Consider what needs to happen if you update a commonly used shlib to fix an important problem but without there being an ABI bump... 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 --------------enig2B523ACB452093961C857935 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/ iEYEARECAAYFAk7kfycACgkQ8Mjk52CukIyDcgCdHS2dMOrvC0Ol8iz88lyYbGvv JtwAn0PUbnqsvARjOeedp7CZkGk/dm8M =cmp+ -----END PGP SIGNATURE----- --------------enig2B523ACB452093961C857935--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EE47F1E.9020104>