Marnie, Senaka I certainly think from a users pov it is nice to have a single script. Frankly for a new user it is not clear as to what script he should run (ex qpid-server, qpid-run, run ..etc). Also instead of fixing the current scripts I think it is better to have single script that covers the existing functionality. This is easy from a maintainence pov as well as from an end user pov.
Regards, Rajith On Tue, May 20, 2008 at 11:56 AM, 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 > > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
