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<w...@widodh.nl>
---
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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
