Date: Sat, 25 Jul 2009 09:16:22 -0800 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Subject: Re: Restarting daemons after portupgrade/portmanager Message-ID: <200907250916.22355.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <4A6A3C49.4090403@glemsk.net> References: <4A6A3C49.4090403@glemsk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200907250916.22355.mel.flynn%2Bfbsd.questions>