Date: Mon, 25 Sep 2006 08:03:59 GMT From: Erwin Van de Velde <erwin.vandevelde@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/103609: Restarting of services after update Message-ID: <200609250803.k8P83x26089288@www.freebsd.org> Resent-Message-ID: <200609250810.k8P8AN9v071229@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 103609 >Category: ports >Synopsis: Restarting of services after update >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Sep 25 08:10:23 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Erwin Van de Velde >Release: 6.1-RELEASE-p1 >Organization: University of Antwerp - PATS >Environment: FreeBSD *.ua.ac.be 6.1-RELEASE-p1 FreeBSD 6.1-RELEASE-p1 #1: Thu Jun 1 09:33:17 CEST 2006 >Description: Almost every port containing a service stops the service before updating but does not restart it afterwards. I was wondering how difficult it can be to restart the updated service after installing the files? In my opinion, it would be less error-prone than hoping for the administrator to remember restarting all updated services... While this depends on every port maintainer, a general guideline about this would help and encourage maintainers to do this. >How-To-Repeat: e.g. update apache22 >Fix: Fix the ports, adding a restart after installation procedure. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609250803.k8P83x26089288>