From owner-freebsd-ports@FreeBSD.ORG Sat Sep 17 09:19:25 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D8E5106566B for ; Sat, 17 Sep 2011 09:19:25 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from erengrad.hoster.bg (erengrad.hoster.bg [77.77.142.9]) by mx1.freebsd.org (Postfix) with ESMTP id DB3188FC12 for ; Sat, 17 Sep 2011 09:19:24 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by erengrad.hoster.bg (Postfix) with ESMTP id 8444EDD09C for ; Sat, 17 Sep 2011 12:19:20 +0300 (EEST) Received: from straylight.m.ringlet.net (unknown [95.111.66.80]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id 37CBB5C27F for ; Sat, 17 Sep 2011 12:18:48 +0300 (EEST) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id dae01e by straylight.m.ringlet.net (DragonFly Mail Agent) Sat, 17 Sep 2011 12:18:47 +0300 Date: Sat, 17 Sep 2011 12:18:47 +0300 From: Peter Pentchev To: freebsd-ports@freebsd.org Message-ID: <20110917091847.GA2754@straylight.m.ringlet.net> Mail-Followup-To: freebsd-ports@freebsd.org References: <4E7247F2.7080207@wasikowski.net> <20110915183710.GA47127@guilt.hydra> <4E7253AF.7030602@wasikowski.net> <4E725782.3090107@gmx.de> <46157122.20110916135126@serebryakov.spb.ru> <4E73709D.5020004@gmx.de> <4E73AADB.8060804@FreeBSD.org> <4E74639E.1060207@gmx.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <4E74639E.1060207@gmx.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-MailScanner-ID: 37CBB5C27F.C2B88 X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: freebsd-ports@freebsd.org X-Spam-Status: No Subject: Re: Re-starting daemons across upgrades? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 09:19:25 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Sep 17, 2011 at 11:08:46AM +0200, Matthias Andree wrote: > Am 16.09.2011 22:00, schrieb Gabor Kovesdan: > >On 2011.09.16. 17:51, Matthias Andree wrote: > >>Am 16.09.2011 11:51, schrieb Lev Serebryakov: > >>>Hello, Freebsd-ports. > >>>You wrote 16 =D1=81=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2011 =D0= =B3., 0:28:07: > >>> > >>>>>Really? I thought it was supposed to be standard > >>>>>behaviour- the @stopdaemon > >>>>>line in pkg-plist facilitates that. > >>>>While I totally understand why we do this, I have to say it's VERY > >>>>VERY annoying behavior especially when one upgrading a remote system > >>>>with multiple server daemon ports. One have to watch the whole > >>>>process carefully and restart the daemon manually. > >>> Yep, and even more annoyingly is that it is completely inconsistent: > >>> some daemons are stopped, some not, etc. > >>We do not currently have a standard procedure for that, nor do we record > >>the necessary state -- perhaps we should just discuss, vote, and add a > >>paragraph to the porter's handbook. > >> > >>We also need to bring the authors (or volunteers) for the de-facto > >>standard upgrade tools into the loop. > >> > >>My thoughts: > >> > >>- give the user a choice to configure whether to restart services > >> > >>- optional: give the users a chance to configure this per-service > >> > >>- discuss whether we want/need to support this (a) in the framework that > >>we currently use, (b) only in pkgng, (c) in portmaster and portupgrade > >>where necessary. > >Or we could have a facility to check whether services are running. > >For example, I have some cron scripts, which are similar for all > >of the services that I'm watching. They run periodically and > >restart services if they are down. It does not matter if they are > >down because of an upgrade or a failure, so this solution is more > >general. Here's an example that I have for MySQL: >=20 >=20 > Before we go that way, we should consider using runit by Gerrit Pape > (smarden.org), Upstart, or port systemd. Or (bet you didn't expect that from a hardcore daemontools user like me ;) our own FreeBSD Services Control - http://people.FreeBSD.org/~trhodes/fsc/ (once it's ready to enter the tree) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org peter@packetscale.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 because I didn't think of a good beginning of it. --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOdGXzAAoJEGUe77AlJ98TdmoQALOdcP6BtzFq8lupWfipuoJa h8O9+E2XxJoNBMeH9TVun0Km1QVDA7ty0dWRxEHbTe7DhdAym3U+2xToN+WxEy01 iVgmN662y3iCNt0Pn9QbBr+VQF5mfmF5pIMmkrOEo36YWFlH0/OpGLj1m7dGSRkc 3FhDAX0OYJezNIBWm1+/lx7Y7MfNSKRdms7vBKE7nSDWWBxjNMzcwMUzDieH3pTT /d3G9QPqTssc/qatELM5+KsvI/X7qU3BKORQSIQqZ6Hz4PQa2CYAnb6WaxjEYHhK KkR9JdkWdCgTWBOSbY+uMCR1q7k+F/liu+k1H+YcrLAErDojFlmkl3PpAj6lRaDN KbEqJTCo8PBHr/skF4BTKaNl4fXqsmxTdW+kBDcW2iBOexewoJa9x21PdYcbsEy8 97gyKAs5MqEm2PmNaFyK3evnEbC+3XICgBdFJNGachKMNHj2q3L5W/AyqMpi/BRz feHwSXIdrVenySu5qs8TDmj/k60cSBteCNFOAZxkfTceIOx7UPkJnWRX+DKP4I5D 18u9U6+m3J4XvFX/2HyUGWBaCt+q3F+8owopu998/sUlWooMzBwtSF9ipgrK+cZ5 EitdMVamt1ci2ndtBfGCWdyFFvxCyof09pnfNm26WniGxF5qSyXN0m5qlaaVpH81 XWWWVC0zajzf4EEyzs3a =D0pY -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0--