Date: Mon, 25 Sep 2006 11:24:52 +0200 From: Armin Pirkovitsch <a.pirko@inode.at> To: Rene Ladan <r.c.ladan@gmail.com> Cc: ports@freebsd.org, Erwin Van de Velde <erwin.vandevelde@ua.ac.be> Subject: Re: Restarting services Message-ID: <4517A064.5080201@inode.at> In-Reply-To: <e890cae60609250214n4ebc0aeal2055d1d03c6b48cc@mail.gmail.com> References: <200609251035.15484.erwin.vandevelde@ua.ac.be> <e890cae60609250214n4ebc0aeal2055d1d03c6b48cc@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rene Ladan wrote: > 2006/9/25, Erwin Van de Velde <erwin.vandevelde@ua.ac.be>: >> Dear all, >> >> 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. >> > Sometimes the configuration changes, making it inadvisable to > automatically restart the service. But automatic restarting should be > possible/desirable (IMO) if the configuration remains the same. Well each server/service would need a program to check the syntax of the current config file to ensure that it will work. Otherwise, imho, you could only try and error which is not a clean solution. -- Armin Pirkovitsch a.pirko@inode.at
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4517A064.5080201>