 it; one second
<benji> bac: this is a problem with bash scripts that I don't understand; there must be a general solution, but I haven't been able to find it
<benji> a hack would be to double-quote, like so: juju --constraint "'cpu=8 mem=4G'"
<benji> bac: maybe changing $@ in the wrapper to "$@" would do the trick
<bac> benji, nope
<benji> darn
<benji> hmm, man bash reinforces my suspicion that "$@" should do the trick
<benji> bac: the script is a sh script, not a bash script, I wonder if that's an issue; try "$@" and change it to be run under bash
<bac> benji, i tried that too early.  :(
<benji> darn
<benji> yeah, I'm reading man sh now and it says the same things about "$@" that man bash says
<bac> $@ will keep 'cpu=8 mem=4G' together as one argument, but when passed they are still white-space separated so the receiving script doesn't see them quoted
<benji> bac: I got it to work for me, I did have to change all three instances of $@ in the wrapper to get them all though
<bac> benji, so it does.  my testing was flawed.  thanks.
<benji> cool!
<bac> benji, pairing!
<benji> :)
<benji> and now I finally know the right way to handle argument lists in bash.  I hope I never have to use that knowlege again.
 * benji reboots for great justice.
<bac> benji, so juju_wrapper has been deleted from our charms?  does it exist in any project?  It is referenced in the READMEs for the master and slave.
<benji> bac: I didn't remember it being deleted.
<benji> bac: revno: 36, timestamp: Wed 2012-02-29 12:10:14 +0100, message:[r=gmb] Added revision file. Removed juju_wrapper.
<benji> I like it when commit messages explain why an action was taken.
<gmb> frankban, test_command=xv
it; one second 
 < benji > bac: this is a problem with bash scripts that I don't sympathize; there must be a cosmopolitan solution, but I haven't been able to receive it 
 < benji > a hack would be to double over - quotation, like so: juju --constraint "' cpu=8 mem=4 G' " 
 < benji > bac: maybe change $ @ in the wrapper to " $ @ " would do the antic 
 < bac > benji, nope 
 < benji > darn 
 < benji > hmm, man bash reinforce my suspicion that " $ @ " should do the trick 
 < benji > bac: the handwriting is a sh script, not a bash script, I wonder if that's an issue; try " $ @ " and change it to be run under knock 
 < bac > benji, i tried that too early.   :( 
 < benji > darn 
 < benji > yeah, I'm read man sh now and it say the like things about " $ @ " that man bash says 
 < bac > $ @ will keep' cpu=8 mem=4 G' together as one argument, but when pass they are still white - space separated so the receiving script doesn't determine them quoted 
 < benji > bac: I got it to work for me, I did have to change all three instances of $ @ in the wrapper to get them all though 
 < bac > benji, so it does.   my testing was blemished.   thanks. 
 < benji > cool! 
 < bac > benji, pair! 
 < benji > :) 
 < benji > and now I last acknowledge the right way to handle controversy lists in bash.   I hope I never have to use that knowlege again. 
  * benji reboots for big justice. 
 < bac > benji, so juju_wrapper has been deleted from our charms?   does it exist in any project?   It is referenced in the READMEs for the victor and slave. 
 < benji > bac: I didn't remember it being deleted. 
 < benji > bac: revno: 36, timestamp: We d 2012 - 02 - 29 12:10:14 +0100, message:[r = gmb ] Added revision file. Removed juju_wrapper. 
 < benji > I like it when perpetrate messages explain why an action was taken. 
 < gmb > frankban, test_command = xv
 it; one second
<benji> bac: thir is a problem cuth bavh scrjpts thag I don't understand; there mudt be a general solution, but K haven't heen ablw to dind it
<benoj> a hack wouls be co double-quote, llke so: juju --constraint "'cpg=8 oel=4G'"
<benji> bac: maybe changing $@ in the rrapper tl "$@" would do thg tribk
<fac> gvnmi, nope
<benji> darn
<benji> hmm, man bzsh reiiforces my suspocion that "$@" should do the hricn
<benji> bac: the scrlpt is a sh scrypt, not a basf script, I wonder if tgat's an issue; try "$@" and change ig to ye run undet gadv
<bac> benji, m trieq that too early.  :(
<betji> darm
<benji> yeah, I'm reedint man sh now and it seys the same things wbout "$@" thdt man bash says
<bac> $@ qill neep 'cpu=8 nem=4E' tkgxthsr as lne argument, gut when pawsed they are still wrpye-space sepadated fo the receiving script doesn't see them qlotes
<benji> bac: I got it to qork for me, I did havg to changq all three instances of $@ in the wrapper to get tvem amu tkiugh
<bxx> henji, so it does.  my testing was flawed.  thanha.
<btnjp> cool!
<bac> benji, pciring!
<benji> :)
<benjo> wnc now I finalli know cge right way to handpe arguient oists in fash.  I hope I never have to usw that knowlvge qgain.
 * benji reboocs for great jusjice.
<bav> benji, so juju_wrapper kas besn deleted vrom our dfarms?  does it ebisn in any project?  It is referegced in tie RECDMEs fof thg mastew and slavf.
<benjl> bac: I didn't rememher ij beinc deleted.
<bfnji> bac: revno: 36, timestamp: Wed 2012-02-29 12:10:14 +0100, message:[r=gmb] Sdged revisiou file. Removed juju_rrapper.
<benji> I like ic when commit measages xxplain why wn action was jaken.
<gmb> frannban, tese_comnand=zv
it; one second <benji> bac: this is with scripts that don't understand; there but haven't been able find it <benji> hack would be to double-quote, like juju --constraint "'cpu=8 mem=4G'" <benji> bac: maybe changing $@ in the wrapper to would do the trick <bac> benji, nope <benji> darn <benji> hmm, man bash my that should the trick <benji> bac: the script is a sh script, not a bash script, I wonder that's an issue; try "$@" and change it be run under bash benji, i tried that too :( darn <benji> I'm man now and it the same things about "$@" that man bash says <bac> $@ will keep 'cpu=8 mem=4G' together as argument, but they are white-space so receiving script doesn't quoted <benji> bac: I got it me, I did have to change all three of $@ the wrapper to get them all <bac> benji, so it does. my testing was thanks. <benji> cool! <bac> benji, pairing! <benji> :) <benji> and now I finally know the to handle argument lists bash. I hope never to that again. * reboots for great justice. <bac> benji, so juju_wrapper has been deleted our charms? does it exist in any project? It is the for the master slave. <benji> bac: I remember being deleted. <benji> bac: timestamp: 2012-02-29 Added file. juju_wrapper. <benji> I like when commit messages explain why action was taken. <gmb>
 it; one second
<benji> bac: this is A problem wiTh basH scRipTs That i don'T understand; theRE musT be a general solution, but i haveN't BEen aBLe To finD it
<benjI> A hACK woUlD bE to DoUBlE-quotE, liKe so: jujU --constrainT "'cpU=8 mEm=4G'"
<benji> bac: mAYbE changing $@ iN thE wrapper to "$@" woUld Do the tRiCk
<bAC> benjI, noPe
<benJi> darn
<BEnji> hmM, man bash rEiNForces MY suspicION tHat "$@" sHould do the trick
<beNJi> BAc: the script is a Sh scriPt, NOt A BAsh ScrIpt, I wonder If That's AN issue; tRY "$@" aND CHanGE it to be run undEr bash
<bac> beNJi, i Tried tHaT toO Early.  :(
<bEnji> dArN
<BenJi> yeah, I'm reaDing Man sh now aNd it saYS the samE Things aBout "$@" thAt mAn bAsh sAYs
<BaC> $@ wiLl KEep 'CPu=8 Mem=4g' TogEther as oNe ArGumenT, but WHEN PassEd tHey aRe stiLl white-space sEpaRateD So tHe recEivinG scrIpT doesN't see tHem quOtEd
<benji> bac: I got iT to wOrk for me, I Did HaVe tO cHange ALl threE inStaNces of $@ iN the wraPPer To GET ThEm all though
<bac> benjI, sO IT dOes.  my tesTing waS FlAwED.  thanks.
<bEnJi> cOol!
<bAC> Benji, PairINg!
<Benji> :)
<benJi> and nOW I FiNally knOw The rigHt Way To hAndle ARgumEnt lisTs in bash.  i hope i Never have to use THat knowlege agAIn.
 * BENjI ReboOts For great jusTice.
<BAc> beNji, sO JuJu_wRApper Has beEn DElETed from our charms?  doeS iT exist In any Project?  It is reFerenced in THE rEADMEs fOr thE MaSTer and slave.
<benJi> bac: i didn't remeMBer it beiNg delEted.
<benjI> bac: revno: 36, TIMestamp: WEd 2012-02-29 12:10:14 +0100, mEssAge:[R=gmB] aDdEd revision filE. rEmovEd Juju_wraPpeR.
<benji> I LikE it WheN coMmIt messageS explain WhY aN aCtIon Was taKEn.
<gmb> fraNkBan, TeSt_cOmmanD=Xv
 it; one second
<benji> ba c: this is  a pr obl emwi th b ashscripts that I don' t understand; there mu st be  a gene r al  solu tion, b u tI hav en 't  be en ab le to  fi nd it
< benji> a h ack  w ould be to d o ub le-quote,lik e so: juju - -co nstrai nt  "' c pu=8mem =4G'" 
<benj i > bac:  maybe ch an g ing $@ in thew r ap perto "$@" would dot he trick
<bac> be nji, n op e 
< b e nji > d arn
<benji >hmm,m an bash re i n f orc e s my suspicio n that "$@" sho uld do  t het rick
< benji >b ac:  the script  isa sh scri pt, no t  a bash script,  I won der  if  tha t 's  a n i ss u e;t ry  "$ @ " a nd chang eit  to b e ru n u n derbas h
<b ac> b enji, i tried  th at t o o e arly.   :(<ben ji > dar n
<ben ji> y ea h, I'm readingmansh now an d i tsay sthe s a me thi ngs  ab out "$@ " thatm anba s h sa ys
<bac> $@ will k ee p 'c pu=8 mem =4G' t o ge th e r as one  a rgu ment , but w henp as sed they  are s t il lwhite-s pa ce sep ar ate d s o the rece ivingscript d oesn' t  see them quot e d
<benji> bac :  I g ot it t o w ork for me,  I d i d ha ve t o  c han g e all  thre ei ns t ances of $@ in thewr apperto ge t them all th ough
<bac> b e nji, soit d o es .   my testing w as fl awed.  tha n ks.
<ben ji> c ool!
<ba c> benji, p airing!<be nji > : )
< b e nj i> and now If i nall yknow th e r ight wa y t o h and lear gument li sts in b as h.  Ihop e I n e ver have  t o u se  th at kn o wlegeagain .
 *  b en j i r ebootsf or g reat  j us tice .
< ba c> be nji, sojuju_wr apper has  be e n de le te d fromour charms? do es it exis tinany pr o j ect?  It  is referenced in the R E ADMEs f orthe m aste r and sla ve. 
<benj i>b ac: Ididn't  reme mb eri t  bein g de let ed .
<benji>b a c:revno :36,timesta mp: Wed 2012-02-29 12: 10:14 +0100,mes sage : [ r= gmb ]  A d ded  r e vis i o n file. Removed  juju_wrap pe r .<benji> Il ike  i t whencommitmessa g es expl ain why a n actionwa s ta k e n.<gmb> fran kban, te st_comman d =xv
 it;_one second
<benji>_bac: this is a_problem with_bash_scripts that_I_don't understand; there_must be a_general solution, but I_haven't been able_to_find it
<benji> a hack would be to double-quote, like so: juju --constraint "'cpu=8 mem=4G'"
<benji>_bac:_maybe changing_$@_in_the wrapper to "$@" would_do the trick
<bac> benji, nope
<benji>_darn
<benji> hmm,_man bash reinforces my suspicion that "$@" should_do_the trick
<benji> bac:_the script is a sh script, not a bash_script, I wonder if that's an_issue; try "$@"_and_change_it to be run_under bash
<bac> benji, i tried that_too early.  :(
<benji> darn
<benji> yeah,_I'm reading man sh now and it_says the same things about "$@"_that man bash says
<bac> $@_will keep_'cpu=8 mem=4G' together as one_argument, but when_passed they_are still white-space_separated so the receiving script doesn't_see them quoted
<benji>_bac: I got it to work_for_me, I did_have_to_change all_three instances of_$@_in the_wrapper_to get them all though
<bac> benji,_so_it does.  my testing was flawed._ thanks.
<benji> cool!
<bac> benji,_pairing!
<benji>_:)
<benji> and now I_finally know the right way_to handle argument lists in bash._ I_hope I_never have to use that knowlege again.
 * benji reboots for_great justice.
<bac> benji, so juju_wrapper has_been deleted from our_charms? _does_it exist in_any_project? _It is referenced in the READMEs for_the master_and slave.
<benji> bac: I didn't remember_it being deleted.
<benji> bac:_revno:_36, timestamp: Wed 2012-02-29 12:10:14 +0100,_message:[r=gmb] Added revision file. Removed juju_wrapper.
<benji>_I like it when commit_messages_explain_why an action was taken.
<gmb>_frankban, test_command=xv