Re-starting daemons across upgrades?

Peter Pentchev roam at ringlet.net
Sat Sep 17 09:19:25 UTC 2011


On Sat, Sep 17, 2011 at 11:08:46AM +0200, Matthias Andree wrote:
> 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.

Or (bet you didn't expect that from a hardcore daemontools user like me ;)
our own FreeBSD Services Control - http://people.FreeBSD.org/~trhodes/fsc/
(once it's ready to enter the tree)

G'luck,
Peter

-- 
Peter Pentchev	roam at ringlet.net roam at FreeBSD.org peter at packetscale.com
PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
because I didn't think of a good beginning of it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20110917/d5920c35/attachment.pgp


More information about the freebsd-ports mailing list