From owner-freebsd-questions@FreeBSD.ORG Sat Jul 25 17:16:24 2009 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 50AFF106564A for ; Sat, 25 Jul 2009 17:16:24 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from mailhub.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 1FE7E8FC16 for ; Sat, 25 Jul 2009 17:16:23 +0000 (UTC) (envelope-from mel.flynn+fbsd.questions@mailing.thruhere.net) Received: from smoochies.rachie.is-a-geek.net (mailhub.lan.rachie.is-a-geek.net [192.168.2.11]) by mailhub.rachie.is-a-geek.net (Postfix) with ESMTP id 67B357E818 for ; Sat, 25 Jul 2009 09:16:23 -0800 (AKDT) From: Mel Flynn To: freebsd-questions@freebsd.org Date: Sat, 25 Jul 2009 09:16:22 -0800 User-Agent: KMail/1.11.4 (FreeBSD/8.0-BETA2; KDE/4.2.4; i386; ; ) References: <4A6A3C49.4090403@glemsk.net> In-Reply-To: <4A6A3C49.4090403@glemsk.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907250916.22355.mel.flynn+fbsd.questions@mailing.thruhere.net> Subject: Re: Restarting daemons after portupgrade/portmanager 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: Sat, 25 Jul 2009 17:16:24 -0000 On Friday 24 July 2009 14:57:13 Axel wrote: > So far, so good. But what about the other daemons that still seem to run > after upgrade (Apache, Courier IMAP etc)? Are the new version running > fine after the upgrade, or should I set AFTERINSTALL to do a restart of > these daemons, to make sure they run the upgraded version? I don't know about Courier, but Apache is generally not affected by on-disk versions of libraries. The CGI programs however, are, since they're started up and shutdown with each request (or in the case of FCGI in X requests) - the Apache workers are spawned from the root process and use that process image. So there is no definite need to shut down Apache and disrupt service. If a running webserver is important to you, I also would not do this automatically. For example, jpeg could be upgraded before Apache and a module for Apache needing it, yet this module is depending on Apache and therefore not recompiled yet. As a result, this module tries to load a non-existing library and Apache restart will fail. -- Mel