Hi Rafi, Some of the echo-ing is really useful when we get users coming along as it does let us see that they've set various variables etc as they believe they have, without them having the debug option set to echo commands etc (i.e. on output they've alredy sent us).
Maybe set it up to be switch off able ? What do you think - though I'm really only focused on qpid-server's use of it so perhaps don't appreciate the generic nuiscence factor so much .... Bfn, Marnie On 7/31/08, Rafael Schloming <[EMAIL PROTECTED]> wrote: > > I recently noticed that the qpid-run script echoes lots of stuff as it > starts things up. This can be quite confusing and annoying when using it to > run simple command-line utilities since the command output is dwarfed by the > amount of stuff echoed by qpid-run. > > Would anyone object if I remove these echo statements? There are already > several options that can be used to see precisely the java command and > classpath used to launch the target program: > > Usage: qpid-run ... [-run:<option>] ... > > Options: > -run:debug > print the classpath and command before running it > > -run:jpda > adds debugging options to the java command, use > JDPA_TRANSPORT and JPDA_ADDRESS to customize the debugging > behavior and use JPDA_OPTS to override it entirely > > -run:external-classpath=<value> > controls how the CLASSPATH environment variable is used by > this script, value can be one of ignore (the default), first, > last, and only > > -run:print-classpath > print the classpath > > -run:print-command > print the command > > -run:help > print this message > > --Rafael >
