From owner-freebsd-ports@FreeBSD.ORG Mon Sep 25 10:01:45 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4899516A403; Mon, 25 Sep 2006 10:01:45 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A80D43D5D; Mon, 25 Sep 2006 10:01:43 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id ECCF5B844; Mon, 25 Sep 2006 13:01:42 +0300 (EEST) Received: (nullmailer pid 96500 invoked by uid 1002); Mon, 25 Sep 2006 10:01:42 -0000 Date: Mon, 25 Sep 2006 13:01:42 +0300 From: Vasil Dimov To: Erwin Van de Velde Message-ID: <20060925100142.GC94311@qlovarnika.bg.datamax> References: <200609251035.15484.erwin.vandevelde@ua.ac.be> <20060925092647.GB94311@qlovarnika.bg.datamax> <200609251147.46990.erwin.vandevelde@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jousvV0MzM2p6OtC" Content-Disposition: inline In-Reply-To: <200609251147.46990.erwin.vandevelde@gmail.com> Cc: freebsd-ports@freebsd.org Subject: Re: Restarting services X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Sep 2006 10:01:45 -0000 --jousvV0MzM2p6OtC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 25, 2006 at 11:47:46AM +0200, Erwin Van de Velde wrote: > On Monday 25 September 2006 11:26, Vasil Dimov wrote: > > IMHO in this case the administrator should be changed, > > not the way ports operate. Building idiot-proof system is impossible and > > leads to the: > > > > Shaw's Principle: > > Build a system that even a fool can use, and only a fool will > > want to use it. >=20 > This is not about being idiot-proof but being handy to use. It also reduc= es=20 > service downtime by immediately restarting the service after update inste= ad=20 > of waiting for the administrator to restart it. I think that implementing this feature the right way would be too complex and would bring too little benefit. By "right way" I mean that a given service should be started upon installation only if it was actually stopped during the upgrade process. Ofcourse if someone thinks that it is worth implementing I would be happy to be asked "service xyz was stopped during upgrade, do you want to start it now?" [y] One could always minimize downtime by doing portupgrade xyz && /usr/local/etc/rc.d/xyz start --=20 Vasil Dimov gro.DSBeerF@dv % If you're happy, you're successful. --jousvV0MzM2p6OtC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFFF6kGFw6SP/bBpCARAtIaAKDHb7s4vYWuQPacCHxU0AwVV1u34wCgq9VQ NYXLHx2Z+EXrU2JCEfikCLU= =oHt0 -----END PGP SIGNATURE----- --jousvV0MzM2p6OtC--