- From: Geoff Meakin <
>
- To:
- Subject: [chef] Re: Chef - no definition for LSB init scripts?
- Date: Mon, 5 Mar 2012 15:16:50 +0000
- Authentication-results: mr.google.com; spf=pass (google.com: domain of
designates 10.180.104.65 as permitted sender)
Apologies, I see this is actually an unresolved bug -
http://tickets.opscode.com/browse/COOK-649
Thanks
On 5 Mar 2012, at 13:04, Geoff Meakin wrote:
>
I note that in Debian squeeze, init has been moved over to LSB-style init
>
scripts.
>
>
Lots of chef modules set up services as follows (e.g. taken from
>
chef-server:)
>
>
service "rabbitmq-server" do
>
if platform?("centos","redhat","fedora")
>
start_command "/sbin/service rabbitmq-server start &> /dev/null"
>
stop_command "/sbin/service rabbitmq-server stop &> /dev/null"
>
end
>
supports [ :restart, :status ]
>
action [ :enable, :start ]
>
end
>
>
>
However, there is no information there about what runlevels it should run
>
in, and consequently on reboot the service does not start. To fix I've had
>
to manually do this to the resultant /etc/init.d/rabbitmq-server:
>
>
### BEGIN INIT INFO
>
# Provides: rabbitmq-server
>
# Required-Start: $remote_fs $network
>
# Required-Stop: $remote_fs $network
>
# Default-Start: 2 3 4 5
>
# Default-Stop: 0 1 6
>
# Description: RabbitMQ broker
>
# Short-Description: Enable AMQP service provided by RabbitMQ broker
>
### END INIT INFO
>
>
>
Is there a chef way of setting this information as Debian has now chosen to
>
follow this new way of controlling boot-time dependency-based startup items.
>
>
Thanks in advance
>
>
Geoff
>
Archive powered by MHonArc 2.6.16.