Date: Sat, 17 Sep 2011 11:08:46 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: Re-starting daemons across upgrades? Message-ID: <4E74639E.1060207@gmx.de> In-Reply-To: <4E73AADB.8060804@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 16.09.2011 22:00, schrieb Gabor Kovesdan: > On 2011.09.16. 17:51, Matthias Andree wrote: >> Am 16.09.2011 11:51, schrieb Lev Serebryakov: >>> Hello, Freebsd-ports. >>> You wrote 16 сентября 2011 г., 0:28:07: >>> >>>>> Really? I thought it was supposed to be standard behaviour- the >>>>> @stopdaemon >>>>> line in pkg-plist facilitates that. >>>> While I totally understand why we do this, I have to say it's VERY >>>> VERY annoying behavior especially when one upgrading a remote system >>>> with multiple server daemon ports. One have to watch the whole >>>> process carefully and restart the daemon manually. >>> Yep, and even more annoyingly is that it is completely inconsistent: >>> some daemons are stopped, some not, etc. >> We do not currently have a standard procedure for that, nor do we record >> the necessary state -- perhaps we should just discuss, vote, and add a >> paragraph to the porter's handbook. >> >> We also need to bring the authors (or volunteers) for the de-facto >> standard upgrade tools into the loop. >> >> My thoughts: >> >> - give the user a choice to configure whether to restart services >> >> - optional: give the users a chance to configure this per-service >> >> - discuss whether we want/need to support this (a) in the framework that >> we currently use, (b) only in pkgng, (c) in portmaster and portupgrade >> where necessary. > Or we could have a facility to check whether services are running. For > example, I have some cron scripts, which are similar for all of the > services that I'm watching. They run periodically and restart services > if they are down. It does not matter if they are down because of an > upgrade or a failure, so this solution is more general. Here's an > example that I have for MySQL: Before we go that way, we should consider using runit by Gerrit Pape (smarden.org), Upstart, or port systemd.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E74639E.1060207>