Date: Fri, 16 Sep 2011 22:34:15 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: =?utf-8?Q?=C5=81ukasz_W=C4=85sikowski?= <lukasz@wasikowski.net> Cc: Matthias Andree <matthias.andree@gmx.de>, Eric <freebsdlists-ports@chillibear.com>, ports-list freebsd <freebsd-ports@freebsd.org> Subject: Re: Re-starting daemons across upgrades? (was: Thank you (for making the ports less boring).) Message-ID: <193113479.20110916223415@serebryakov.spb.ru> In-Reply-To: <4E7392D6.4060309@wasikowski.net> References: <CA99352D.219D1%freebsdlists-ports@chillibear.com> <4E7392D6.4060309@wasikowski.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, =C5=81ukasz. You wrote 16 =D1=81=D0=B5=D0=BD=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2011 =D0=B3.,= 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. --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?193113479.20110916223415>