rabbitmq-discuss_efine at usa.net
Mon Nov 10 19:12:42 GMT 2008
On Mon, Nov 10, 2008 at 12:42 PM, Ben Hood <0x6e6562 at gmail.com> wrote:
> On Mon, Nov 10, 2008 at 4:46 PM, Edwin Fine
> <rabbitmq-discuss_efine at usa.net> wrote:
> > I could send you the contents of the directories of the rabbit_common and
> > erlang_client (after all, it IS your code, just massaged a bit) if you
> Cool. I'm just wondering if it is better to say put it on something
> like bitbucket rather than just lobbing it over the fence - that way
> it may remain tractable for other people - and you might be able to
> just clone the existing Rabbit repo there.
Ah, sorry, I didn't mean send it to you for the purpose of publication, I
meant send it to you for you to see how I've structured it. I don't want to
repackage rabbit for public consumption, unless it is using faxien and
sinan, because then it's as simple as adding one more DAV http address to my
publication repositories. Also, sometimes I have to slightly modify the
client to suit my circumstances, and it's nekulturny to publish your own
mods as an "official" Rabbit build. I would be leery of downloading
something like that!
> BTW how do you start and stop Rabbit, or make it come up on boot?
I use a pretty vanilla /etc/init.d script, and put a call to it into
boot.local, e.g. /etc/init.d/rabbitmq start. To start and stop from the
command line I call the same script. The only downside to this technique is
that if, for some reason, rabbit takes longer than expected to come up (say,
due to recovery of some sort), TCP/IP client applications that come up
before it's ready and depend on it are going to have problems when they try
to use it, so quite a bit of error detection and recovery are necessary
(anyway, that is needed for the case where rabbit may get taken down without
taking the apps down first).
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss