summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDavid Wragg <dpw@lshift.net>2009-09-01 17:15:15 +0100
committerDavid Wragg <dpw@lshift.net>2009-09-01 17:15:15 +0100
commit9ebd102763f797eaa39d2e19b9ab9b0d24b93501 (patch)
tree077a61d16f501e0b4d5a98c3c783aeca4c5f0fb9
parente3a94b0accf234dcaae542ff13054e8f0d8b95bb (diff)
downloadrabbitmq-server-bug21415.tar.gz
Don't 'chkconfig --del rabbitmq-server' when upgrading.bug21415
This would disable the service even after the sysadmin has decided to enable it at cetain runlevels. Since this 'chkconfig --del' only happens during an upgrade, and is always followed by a 'chkconfig --add' anyway during %post, removing it should be safe.
-rw-r--r--packaging/RPMS/Fedora/rabbitmq-server.spec3
1 files changed, 1 insertions, 2 deletions
diff --git a/packaging/RPMS/Fedora/rabbitmq-server.spec b/packaging/RPMS/Fedora/rabbitmq-server.spec
index 7f442831..5dcc3611 100644
--- a/packaging/RPMS/Fedora/rabbitmq-server.spec
+++ b/packaging/RPMS/Fedora/rabbitmq-server.spec
@@ -74,9 +74,8 @@ echo '%defattr(-,root,root, -)' >> %{_builddir}/filelist.%{name}.rpm
%pre
if [ $1 -gt 1 ]; then
- #Upgrade - stop and remove previous instance of rabbitmq-server init.d script
+ # Upgrade - stop previous instance of rabbitmq-server init.d script
/sbin/service rabbitmq-server stop
- /sbin/chkconfig --del rabbitmq-server
fi
# create rabbitmq group