Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
Lev Serebryakov wrote: Hello, Łukasz. You wrote 16 сентября 2011 г., 22:17:58: were not recompiled). Updating ports should never turn off or restart service - thats my $0.02. I agree with that. It is not difficult to REstart service by hands. But stopping service is another story. Many ports/packages stop service on dinstall/pkg_delete, and as result, if port with service are upgraded in the middle of large upgrade session (and it is not always possible to upgrade services SEPARATELY, due to dependences), here is large window when old service is stopped, but new cannot be started yet. From my point of view, it is better to not stop the service by deinstall phase, if it is not started by install. If I do portmaster -a, deinstall of MySQL stops the mysql daemon and all dependent services are unavailable for a very long time - until all other packages are upgraded and administrator starts MySQL by hand. It can be hours. But I like the idea based on portupgrade AFTERINSTALL / (AFTERUPGRADE) - some kind of custom hooks, where user can define actions for specific packages / services. It can be restart in some cases, or write something to log, or send an e-mail, or print some user defined warning text about dependencies needed to be upgraded / restarted... and so on. Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
W dniu 2011-09-16 20:25, Chris Rees pisze: > However, having services not restarted after an upgrade can leave you > with a) a vulnerable older service and b) a nasty shock when you > decide to reboot six months later and it breaks :) I know that I should restart service after update and I will do it, I promise :) But I like to do it when I'm prepared for it, not when monitoring system starts screaming about a down service ;) -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
Hello, Łukasz. You wrote 16 сентября 2011 г., 22:17:58: > were not recompiled). Updating ports should never turn off or restart > service - thats my $0.02. I agree with that. It is not difficult to REstart service by hands. But stopping service is another story. Many ports/packages stop service on dinstall/pkg_delete, and as result, if port with service are upgraded in the middle of large upgrade session (and it is not always possible to upgrade services SEPARATELY, due to dependences), here is large window when old service is stopped, but new cannot be started yet. -- // Black Lion AKA Lev Serebryakov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
2011/9/16 Łukasz Wąsikowski : > W dniu 2011-09-16 18:17, Eric pisze: > >> Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using >> AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart. > > I'm using it for a long time on my personal box and it's not that great. > After some updates there is need to prepare the daemon - adjust > configuration for example. Automatic restart will do much harm in that > case. Another example: update when there's apache and php in new > versions, system has also eaccelerator and some pecl's installed. If php > was updated before apache, then apache restart via AFTERINSTALL will > leave you with not working www server (because eaccelerator and pecl's > were not recompiled). Updating ports should never turn off or restart > service - thats my $0.02. > I had a thought about implementing this in bsd.port.mk, but to tell the truth it would be better handled by your port manager of choice-- I can't find an option for portmaster, but I bet someone willing to send a working patch to dougb can earn themselves some brownie points. I would do it myself, but meh it doesn't upset me that much. However, having services not restarted after an upgrade can leave you with a) a vulnerable older service and b) a nasty shock when you decide to reboot six months later and it breaks :) Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
W dniu 2011-09-16 18:17, Eric pisze: > Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using > AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart. I'm using it for a long time on my personal box and it's not that great. After some updates there is need to prepare the daemon - adjust configuration for example. Automatic restart will do much harm in that case. Another example: update when there's apache and php in new versions, system has also eaccelerator and some pecl's installed. If php was updated before apache, then apache restart via AFTERINSTALL will leave you with not working www server (because eaccelerator and pecl's were not recompiled). Updating ports should never turn off or restart service - thats my $0.02. -- best regards, Lukasz Wasikowski ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
> 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. Just for ref regarding (c) on the portupgrade wiki page[1] it mentions using AFTERINSTALL in pkgtools.conf for doing automatic stop/start/restart. [1] http://wiki.freebsd.org/portupgrade ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).)
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. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
