<br><br><div class="gmail_quote">On Mon, Nov 10, 2008 at 12:42 PM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ed,<br>
<br>
On Mon, Nov 10, 2008 at 4:46 PM, Edwin Fine<br>
<div class="Ih2E3d"><<a href="mailto:rabbitmq-discuss_efine@usa.net">rabbitmq-discuss_efine@usa.net</a>> wrote:<br>
</div><div class="Ih2E3d">> I could send you the contents of the directories of the rabbit_common and<br>
> erlang_client (after all, it IS your code, just massaged a bit) if you want.<br>
<br>
</div>Cool. I'm just wondering if it is better to say put it on something<br>
like bitbucket rather than just lobbing it over the fence - that way<br>
it may remain tractable for other people - and you might be able to<br>
just clone the existing Rabbit repo there.</blockquote><div><br>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!<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
BTW how do you start and stop Rabbit, or make it come up on boot?</blockquote><div><br>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). <br>
<br>Ed</div></div><br>