[rabbitmq-discuss] Using init.d vs upstart script on EC2 image

[Marek Majkowski]

Thanks for suggestion.

Do you think our main ubuntu package should also use upstart,
or is it only relevant for EC2?

Is it compatible with debian?

Cheers,
  Marek

On Fri, Jul 16, 2010 at 15:40, Reza Lotun <rlotun at gmail.com> wrote:
> Hi All,
>
> I currently have a RabbitMQ node deployed on EC2. I used your 64-bit
> image from here:
> http://www.rabbitmq.com/ec2.html
>
> The default setup for this image works. However, I noticed that the
> config scripts use a standard /etc/init.d init script. Since you're on
> ubuntu, I'd suggest using an upstart (http://upstart.ubuntu.com)
> config - mainly because it allows respawning processes. So, if the
> queue broker dies for whatever reason, upstart can be configured to
> automatically restart it.
>
> A simple example config:
>
> ---
> description "RabbitMQ Server"
> author  "RabbitMQ"
>
> start on runlevel 2
> start on runlevel 3
>
> stop on runlevel 0
> stop on runlevel 1
> stop on runlevel 4
> stop on runlevel 5
> stop on runlevel 6
>
> exec /usr/sbin/rabbitmq-multi start_all 1 >
> /var/log/rabbitmq/startup_log 2> /var/log/rabbitmq/startup_err
> respawn
> ----
>
> And then to use it:
>
> cp rabbitmq-server.conf /etc/init
> sudo initctl reload-configuration
> sudo start rabbitmq-server
>
> Has anyone else done something similar?