From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wido den Hollander Subject: Re: [PATCH] debian init: Do not stop or start daemons when installing or upgrading Date: Wed, 16 Nov 2011 22:01:23 +0100 Message-ID: <4EC424A3.7080406@widodh.nl> References: <1321472475-19115-1-git-send-email-wido@widodh.nl> <1321472475-19115-2-git-send-email-wido@widodh.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtp02.mail.pcextreme.nl ([109.72.87.138]:41858 "EHLO smtp02.mail.pcextreme.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752021Ab1KPVB0 (ORCPT ); Wed, 16 Nov 2011 16:01:26 -0500 In-Reply-To: Sender: ceph-devel-owner@vger.kernel.org List-ID: To: Sage Weil Cc: gcs@debian.hu, ceph-devel@vger.kernel.org On 11/16/2011 08:53 PM, Sage Weil wrote: > Ooh, that would certainly make things less annoying for me as well. > Unless that's contrary to some debian policy/best practice, Laszlo? > We could also go for "--no-restart-on-upgrade". I ran into this when upgrading the debs on my machines. The init script would try to stop any running radosgw processes, that failed (none were running), exited non-zero and that broke the prerm script. But since we are dealing with potentially very important daemons I don't want any init scripts restarting my daemons, I want to do that myself. Wido > sage > > > On Wed, 16 Nov 2011, Wido den Hollander wrote: > >> >> Signed-off-by: Wido den Hollander >> --- >> debian/rules | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/debian/rules b/debian/rules >> index a20258d..4f3fe62 100755 >> --- a/debian/rules >> +++ b/debian/rules >> @@ -98,7 +98,7 @@ binary-arch: build install >> dh_installexamples >> dh_install --sourcedir=$(DESTDIR) --list-missing >> dh_installlogrotate >> - dh_installinit >> + dh_installinit --no-start >> dh_installman >> dh_lintian >> dh_link >> -- >> 1.7.5.4 >> >> -- >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> >>