Hi again, /usr/lib should be corrected as /usr/bin
Thanks, Senaka On Tue, May 20, 2008 at 9:41 PM, Senaka Fernando <[EMAIL PROTECTED]> wrote: > Hi Marnie, > > I was thinking about investing in the possibility that someday we could do > a decent installation of Qpid Java and add this single script to /usr/lib. > Having several scripts is going to be a bit messy in this sense. > > I don't think this requires severe re-writing as long as you get the thing > properly organized. Also, there are other benefits such as easy-to-handle > cross platform support. > > Regards, > Senaka > > > On Tue, May 20, 2008 at 9:26 PM, Marnie McCormack < > [EMAIL PROTECTED]> wrote: > >> Hi Senaka, >> >> I'm not sure how much weight I'd put into this area as the scripts more or >> less do as they should, and aside from qpid-run they're fairly >> lightweight. >> I think there may be a couple of open JIRAs for the stop scritps around >> different ps options/platforms. They might be helpful fixes to have. >> >> Thanks & Reards, >> Marnie >> >> >> On 5/20/08, Senaka Fernando <[EMAIL PROTECTED]> wrote: >> > >> > Hi all, >> > >> > At the moment we have a collection of unix shell scripts managing the >> > running of the Java Broker. >> > >> > qpid-run >> > qpid-server >> > qpid.start >> > qpid.stop >> > qpid.stopall >> > run.sh >> > >> > This makes it quite un-manageable. My intension is to provide something >> > similar to apache2ctl which is used to start/stop the httpd. >> > >> > Using this mechanism, it will be possible to have one script, qpid or >> > qpidctl (we need to figure out a nice name), and then call it as >> required. >> > >> > Ex:- qpidctl start or qpidctl stopall >> > >> > I believe that this is more uniform and efficient than the current >> setup. >> > >> > Regards, >> > Senaka >> > >> > >
