Date: Fri, 16 Sep 2011 21:37:37 +0200 From: =?ISO-8859-2?Q?=A3ukasz_W=B1sikowski?= <lukasz@wasikowski.net> To: Chris Rees <crees@freebsd.org> Cc: Matthias Andree <matthias.andree@gmx.de>, lev@freebsd.org, 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: <4E73A581.7040500@wasikowski.net> In-Reply-To: <CADLo839dxMAS2Akioi=T3CN3ch4HrH69eyH0LzP6qvUtnzgCuA@mail.gmail.com> References: <CA99352D.219D1%freebsdlists-ports@chillibear.com> <4E7392D6.4060309@wasikowski.net> <CADLo839dxMAS2Akioi=T3CN3ch4HrH69eyH0LzP6qvUtnzgCuA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E73A581.7040500>