Unless anyone believes that the current changes will break suse as they
currently stand, I need to get things merged -- we cannot proceed in our
testing efforts on Ubuntu with a busted rabbitmq barclamp.


On Thu, May 30, 2013 at 11:54 AM, Vincent Untz <notifications@github.com>wrote:

> In chef/cookbooks/rabbitmq/recipes/default.rb:
>
> > @@ -28,12 +28,17 @@
> >  #  action :add
> >  #end
> >
> > -# rabbitmq-server is not well-behaved as far as managed services goes
> > -# we'll need to add a LWRP for calling rabbitmqctl stop
> > -# while still using /etc/init.d/rabbitmq-server start
> > -# because of this we just put the rabbitmq-env.conf in place and let it rip
> > +execute "stop rabbitmq" do
> > +  command "rabbitmqctl stop; ps aux |awk '/^rabbit/ {print $2}' |xargs kill || :"
> > +  only_if "which rabbitmqctl && rabbitmqctl status"
> > +  action :nothing
>
> Hrm, I don't think this is caused by distro-specific special-casing. As
> far as I can tell, this would be because we install the package earlier
> now. I don't know why this was needed, though. @rhafer<https://github.com/rhafer>do you remember why?
>
> Btw, looking more closely at this recipe: why does it create the rabbitmq
> user as well as the /var/{log,lib}/rabbitmq directories? Don't all
> rabbitmq-server packages on all distros do this? I just checked, and on
> Ubuntu Lucid, it seems to be handled by the package already.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/crowbar/barclamp-rabbitmq/pull/2/files#r4461566>
> .
>