From owner-freebsd-ports@FreeBSD.ORG Wed Sep 28 20:40:39 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 7E2D21065675 for ; Wed, 28 Sep 2011 20:40:39 +0000 (UTC) (envelope-from lukasz@wasikowski.net) Received: from bijou.wasikowski.net (bijou.wasikowski.net [IPv6:2001:808:10f::1]) by mx1.freebsd.org (Postfix) with ESMTP id 20ACF8FC12 for ; Wed, 28 Sep 2011 20:40:38 +0000 (UTC) Received: from bijou.wasikowski.net (localhost [127.0.0.1]) by bijou.wasikowski.net (Postfix) with ESMTP id 70E465C01A; Wed, 28 Sep 2011 22:40:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at wasikowski.net Received: from bijou.wasikowski.net ([127.0.0.1]) by bijou.wasikowski.net (bijou.wasikowski.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53wa2Mdv0Fo8; Wed, 28 Sep 2011 22:40:32 +0200 (CEST) Received: from [192.168.168.3] (leeloo.unixgroup.pl [62.121.126.31]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by bijou.wasikowski.net (Postfix) with ESMTPSA id 760F25C063; Wed, 28 Sep 2011 22:40:31 +0200 (CEST) Message-ID: <4E83863E.3040607@wasikowski.net> Date: Wed, 28 Sep 2011 22:40:30 +0200 From: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: Matthias Andree References: <20110912230943.GD33455@guilt.hydra> <4E6E99BC.4050909@missouri.edu> <1315905051.1747.208.camel@xenon> <4E6F8A50.9060205@gmx.de> <1315942042.1747.258.camel@xenon> <4E6FD71D.9010207@gmx.de> <20110914181553.f6d31b0f.cjr@cruwe.de> <4E722F3F.3030606@wasikowski.net> <20110915180815.GA46983@guilt.hydra> <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> <4E7657AA.1050906@wasikowski.net> <4E836D2F.3070708@gmx.de> In-Reply-To: <4E836D2F.3070708@gmx.de> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org 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: Wed, 28 Sep 2011 20:40:39 -0000 W dniu 2011-09-28 20:53, Matthias Andree pisze: >> We shouldn't go that way at all. Restarting service right after it's >> update is not a good thing. In many cases service will not start, >> because of needed configuration changes od other ports not recompiled or >> updated. The safe way is to not stop service at all. Let the system >> operator restart service manually when he finish all the needed update >> tasks. > > Well, the maintainer should know if the service can be restarted or > needs manual intervention. For patch level upgrades - pathological cases > like OpenLDAP or Cyrus-SASL interactions aside - you normally can > restart the service without further ado. That's true. Still, I often like to update software during the work hours and restart it in the middle of the night. It's not as annoying to customers as restarting critical service during peak hours. Restart time should be left for operator to decide. -- best regards Lukasz Wasikowski