From owner-freebsd-ports@FreeBSD.ORG Thu Oct 27 11:06:46 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 D594D106567D for ; Thu, 27 Oct 2011 11:06:46 +0000 (UTC) (envelope-from ml@netfence.it) Received: from cp-out8.libero.it (cp-out8.libero.it [212.52.84.108]) by mx1.freebsd.org (Postfix) with ESMTP id 4F4788FC12 for ; Thu, 27 Oct 2011 11:06:46 +0000 (UTC) X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A0B020B.4EA93B44.013A,ss=1,re=0.000,fgs=0 X-libjamoibt: 1555 Received: from soth.ventu (151.41.160.208) by cp-out8.libero.it (8.5.133) id 4E68B78607491DB9 for freebsd-ports@freebsd.org; Thu, 27 Oct 2011 13:06:44 +0200 Received: from alamar.ventu (alamar.ventu [10.1.2.18]) by soth.ventu (8.14.5/8.14.4) with ESMTP id p9RApD26038604 for ; Thu, 27 Oct 2011 12:51:13 +0200 (CEST) (envelope-from ml@netfence.it) Message-ID: <4EA937A1.6070102@netfence.it> Date: Thu, 27 Oct 2011 12:51:13 +0200 From: Andrea Venturoli User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; it-IT; rv:1.9.2.23) Gecko/20110930 Thunderbird/3.1.15 MIME-Version: 1.0 To: freebsd-ports@freebsd.org References: <20111027091500.GM63910@hoeg.nl> In-Reply-To: <20111027091500.GM63910@hoeg.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.72 on 10.1.2.13 Subject: Re: ports/162049: The Ports tree lacks a framework to restart services 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: Thu, 27 Oct 2011 11:06:46 -0000 On 10/27/11 11:15, Ed Schouten wrote: I believe you have a point there. > What really bothers me when I use the FreeBSD Ports tree on one of my > systems, is that the behaviour of dealing with services is quite > inconsistent. As mentioned in the PR: > > - If I upgrade Apache, MySQL or PostgreSQL, it does not restart the > service, meaning it won't use the freshly installed daemon. This has > potential security issues. > > - If I upgrade Dovecot, it shuts it down during the upgrade, but won't > restart it. This means that I have to watch portmaster to complete and > must not forget to restart Dovecot afterwards. So does dhcpserver, unfortunately. I'll also add a *really minor* glitch: during upgrade, some ports will leave their daemons running, but somehow break the rc.d scripts, so that you need to manually kill them before you can correctly restart them (e.g. saslauthd). IMVVVHO, I'd be pleased to have the port upgrading process do nothing and leave it to me to restart anything required. I'm inclined to think that, if some port upgrade process stops a daemon, there must be a reason behind this: possibly the port wouldn't upgrade properly otherwise. In this case I'd really like the port to stop and wait for me to press enter just before doing this. The reason is simple: if I launch a "portupgrade -a", taking potentially days, services will stop over time without any way for me to predict when and I can't possibly watch for hours. If they just stopped before killing a service, I could look from time to time and be prepared to restart it in a few minutes (just the time for a single port's "make install"). Just my two cents... bye av.