From owner-freebsd-questions@FreeBSD.ORG Tue Aug 17 08:17:27 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EC141065673 for ; Tue, 17 Aug 2010 08:17:27 +0000 (UTC) (envelope-from SRS0=85Qwagrj=PW=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from atom.beatsnet.com (cl-37.zrh-02.ch.sixxs.net [IPv6:2001:1620:f00:24::2]) by mx1.freebsd.org (Postfix) with ESMTP id 79DAD8FC1D for ; Tue, 17 Aug 2010 08:17:26 +0000 (UTC) Received: from Beat-Siegenthalers-MacBook-Pro.local ([IPv6:2001:1620:f14:0:226:bbff:fe1a:6f6f]) (authenticated bits=0) by atom.beatsnet.com (8.14.4/8.14.4) with ESMTP id o7H8HN8g031774 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 17 Aug 2010 10:17:24 +0200 (CEST) (envelope-from beat.siegenthaler@beatsnet.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beatsnet.com; s=ATOM_DKIM; t=1282033044; bh=IfqmXu9m9qmHvqKRebeit/dM0vtgWHZLBGVsoRSOY1s=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=MnesXeEbeDdlt2MDO3oS1hGYnYIJpZkd+A9KWdZ4HBEpsKYVk2rneq/A6/3oZx7Kz sgAd9bFFcHh2xHwi/0kIQTuGE4MLFyLvKj8LlkNpDCA6DD3vv8d1b4FX3/Hq/tL69P sXDjpSBUx3yqUyd5fNrAyq7tWaISX0uNX6T2znXo= Message-ID: <4C6A4593.8030405@beatsnet.com> Date: Tue, 17 Aug 2010 10:17:23 +0200 From: Beat Siegenthaler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4C69D13F.9080404@dannysplace.net> <20100817032327.0349772b.freebsd@edvax.de> <84y6c6rnpp.fsf@shroyer.name> In-Reply-To: <84y6c6rnpp.fsf@shroyer.name> X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (atom.beatsnet.com [IPv6:2001:1620:f14::1]); Tue, 17 Aug 2010 10:17:24 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.96.2 at atom.beatsnet.com X-Virus-Status: Clean Subject: Re: Upgrading ports while processes are running. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2010 08:17:27 -0000 On 17.08.10 04:13, Mark Shroyer wrote: > That isn't to say you won't see any negative consequences from > overwriting a running port with a newer version. Hypothetically, you > might install a new Python including a new standard library, and if your > running (old) Python process tries to load one of its deleted modules > from disk something could break. Or not; I'm no expert on the ports > system, they might have some way of working around this. But as for a > pragmatic answer to your question, I err on the side of caution with > this stuff Wow, thanks for this perfect description how this is working. For my part, I am updating since many years regularly the ports. Never stop any daemon before. But after the upgrade I restart the daemon if it is something like apache, clamav, some milters, mysql. It never causes trouble. The only thing that if I use restart, rc says the daemon is not running (but running fine) . But after reading Your article it is now clear why. Beat