[rabbitmq-discuss] Suggested small changes to /etc/init.d/rabbitmq-server

Terry Jones terry at fluidinfo.com
Tue Jul 14 06:24:43 BST 2009

It would be nice if /etc/init.d/rabbitmq-server allowed one to customize
where it writes the output that currently goes to /var/log/rabbitmq.

Attached is a trivial diff to allow the directory for those files to be set
in /etc/default/rabbitmq

There are a few other small things I'd do to that script too, were it mine.

Is there any decent reason why the scripts in /usr/sbin/rabbit-* refuse to
run rabbitmq unless you're root?  Seeing as a normal user can directly run
/usr/lib/rabbitmq/bin/rabbit-*, I don't really see the point of denying a
normal user in /usr/sbin/rabbit-*.  The /usr/sbin scripts could check to
see if you're root and use su rabbitmq if so, and just run as the user if
not. The worst that can happen is that rabbit fails to start, isn't it?

I ask all this because I'm upgrading some automated scripts to a modern
version of RabbitMQ after Esteve Fernandez noticed I was running 1.4. Last
time, I went behind the back of the normal rabbit startup scripts (using
rabbitmqctl_real) to get things done as a normal user. It would be nice to
just be able to run /etc/init.d/rabbit-server and not to have to hack it
again this time (and next time, if something like rabbitmqctl_real appears
or disappears behind the scenes). But the /var/log and the /usr/sbin root
check don't want to let me do that.



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: rabbit-diff
Url: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090714/dde5d80f/attachment.txt 

More information about the rabbitmq-discuss mailing list