Thanks, Chris. From my reading, I agree that $@ looks safer. I ran this example on Mac OS X. Seems like $@ is the desired behavior.
http://www.tldp.org/LDP/abs/html/internalvariables.html#INCOMPAT On Mon, Jan 26, 2015 at 12:52 PM, Chris Riccomini <[email protected]> wrote: > Hey Roger, > > Good catch. I've merged and committed. I noticed that there's also a $* > approach to this. Cursory digging indicates that "$@" is safter, though. > > Cheers, > Chris > > On Mon, Jan 26, 2015 at 10:09 AM, Roger Hoover <[email protected]> > wrote: > > > Hi all, > > > > I ran into an issue passing config options to run-class.sh and > run-job.sh. > > Those scripts are not passing through all arguments verbatim but instead > > applying shell expansion over and over. > > > > The right way to do it is to use quotes "$@" ( > > http://www.ibm.com/developerworks/linux/library/l-bash2/#acceptargue) > > > > I opened a JIRA ticket here: > > > > https://issues.apache.org/jira/browse/SAMZA-530 > > > > Cheers, > > > > Roger > > >
