Date: Wed, 28 Sep 2011 20:53:35 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= <lukasz@wasikowski.net> Cc: freebsd-ports@freebsd.org Subject: Re: Re-starting daemons across upgrades? Message-ID: <4E836D2F.3070708@gmx.de> In-Reply-To: <4E7657AA.1050906@wasikowski.net> References: <20110912230943.GD33455@guilt.hydra> <4E6E99BC.4050909@missouri.edu> <1315905051.1747.208.camel@xenon> <4E6F8A50.9060205@gmx.de> <1315942042.1747.258.camel@xenon> <4E6FD71D.9010207@gmx.de> <20110914181553.f6d31b0f.cjr@cruwe.de> <4E722F3F.3030606@wasikowski.net> <20110915180815.GA46983@guilt.hydra> <4E7247F2.7080207@wasikowski.net> <20110915183710.GA47127@guilt.hydra> <4E7253AF.7030602@wasikowski.net> <4E725782.3090107@gmx.de> <CADLo839_KJZGpjYcdFM1a3jqGCg4EHrz08xnNEQ30uW2c4uz7w@mail.gmail.com> <CAGMYy3vugL=YVqzH6-u81dLitgZU55tEnuuBnfqwyg86Wf9t3g@mail.gmail.com> <46157122.20110916135126@serebryakov.spb.ru> <4E73709D.5020004@gmx.de> <4E73AADB.8060804@FreeBSD.org> <4E74639E.1060207@gmx.de> <4E7657AA.1050906@wasikowski.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 18.09.2011 22:42, schrieb Łukasz Wąsikowski: > We shouldn't go that way at all. Restarting service right after it's > update is not a good thing. In many cases service will not start, > because of needed configuration changes od other ports not recompiled or > updated. The safe way is to not stop service at all. Let the system > operator restart service manually when he finish all the needed update > tasks. Well, the maintainer should know if the service can be restarted or needs manual intervention. For patch level upgrades - pathological cases like OpenLDAP or Cyrus-SASL interactions aside - you normally can restart the service without further ado.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E836D2F.3070708>