 ear off. If a job fails to start.. it will be stop/waiting.. but startpar will wait for it forever.... ideas?
<slangasek> hmm
<slangasek> isn't that the same thing startpar does with an init script that fails?
<SpamapS> I dont know
<slangasek> I'm pretty sure it is
<SpamapS> I thought it would mark it as FAIL
<slangasek> oh
<SpamapS> and still finish the boot
<slangasek> yeah, you could be right
<slangasek> in which case, we would need to extend the startpar bridge to handle this case
<slangasek> I'm not too enthusiastic about this; the startpar bridge was always intended to be a short-term transitional solution
<SpamapS> You should get the stopped RESULT=# event.. but you might have missed it. :-P
<SpamapS> slangasek: Understood. I'm happy to help. This is a side project of mine at the moment. :)
<slangasek> we probably are getting the stopped RESULT=# event, but we aren't doing anything meaningful with the $RESULT
<SpamapS> slangasek: so this particular job is start on (filesystem and started rsyslog)..
<SpamapS> slangasek: and it fails in < 1s
<SpamapS> slangasek: so I'm guessing startpar is nearly always going to miss that
<SpamapS> unless they're queued up or something
<slangasek> which they aren't, I'm afraid
<slangasek> (why is it'start on filesystem and started rsyslog' instead of'start on started rsyslog', given that rsyslog starts on filesystem?)
<SpamapS> slangasek: cribbed from ubuntu I'm sure
<SpamapS> it should probably just be start on started rsyslog
<SpamapS> but even then.. :-P
<slangasek> yep
<SpamapS> this is cloud-config
<SpamapS> it could probably just be'start on stopped rc RUNLEVEL=[2345]' in Ubuntu..
<SpamapS> but with the current scheme, nothing
ear off. If a job fails to start.. it will be stop / expect.. but startpar will expect for it forever.... ideas? 
 < slangasek > hmm 
 < slangasek > isn't that the like thing startpar do with an init script that fails? 
 < SpamapS > I do nt acknowledge 
 < slangasek > I'm pretty sure it is 
 < SpamapS > I think it would mark it as FAIL 
 < slangasek > oh 
 < SpamapS > and still eat up the boot 
 < slangasek > yeah, you could be right 
 < slangasek > in which sheath, we would necessitate to extend the startpar bridge to handle this case 
 < slangasek > I'm not too enthusiastic about this; the startpar bridge was always intend to be a short - term transitional solution 
 < SpamapS > You should get the stop RESULT= # event.. but you might have missed it. :-P 
 < SpamapS > slangasek: Understood. I'm happy to help. This is a slope project of mine at the moment. :) 
 < slangasek > we probably are getting the stopped RESULT= # consequence, but we aren't doing anything meaningful with the $ RESULT 
 < SpamapS > slangasek: so this particular job is start on (filesystem and started rsyslog).. 
 < SpamapS > slangasek: and it fail in < 1s 
 < SpamapS > slangasek: so I'm guessing startpar is nearly always going to miss that 
 < SpamapS > unless they're queued up or something 
 < slangasek > which they aren't, I'm afraid 
 < slangasek > (why is it'start on filesystem and started rsyslog' instead of'start on started rsyslog', contribute that rsyslog starts on filesystem ?) 
 < SpamapS > slangasek: cribbed from ubuntu I'm sure 
 < SpamapS > it should credibly barely be begin on started rsyslog 
 < SpamapS > but even then.. :-P 
 < slangasek > yep 
 < SpamapS > this is cloud - config 
 < SpamapS > it could probably barely be'start on stopped rc RUNLEVEL=[2345 ]' in Ubuntu.. 
 < SpamapS > but with the current scheme, nothing
 eag off. If a job fails to rtart.. it will bg wtop/wamting.. bht startoar will wait for it forever.... ieeas?
<soangasek> hmm
<slangasek> ksn't that the samw thmng startpar does with ak inif scrnpv that fails?
<SpakapS> I dond know
<slangasen> K'm pretty sure it is
<SpamapS> I thought it woukd mark it as FAYL
<slsggassk> oh
<SpamapS> and still finish the goot
<slaigasek> yeah, you could be right
<slangasek> ij whlch case, we would jeed to extghd eye startpar cridge to handle this dase
<slangasek> I'm not too enthuskastie about thiw; rhe vtartpar brmdge wws always inbvnded tm be a xhort-term tranxitmonao solution
<SpamapS> You should get the stjpped RESGLC=# event.. but you might hqve mhsseg it. :-P
<SpxmakS> xlzngasen: Uiderstood. I'j happy to yelp. This is a side pwiject of mine at thq ioment. :)
<slangasek> we probably are gettinc tge stopped RESULT=# event, but we aren't doing ajything mqaningful with the $RESULT
<SpamapS> slangasek: so thiv parvizulcv gib is start on (filesystem and started rsyslog)..
<SpwjakS> xlangasek: and lt fails in < 1s
<SpamspD> xjangasek: so I'o guessinf startpar is nearpy alwais goibg to misf thst
<SpamapS> unless they're queyed up or soiwthing
<slangasek> whnch they areu't, I'm sfraic
<slangasek> (why is it'staxt on rilesystem wnd startsa rsyslog' insteaa on'stdrt on suxrted rsyslog', givqn that rwyslpg stargs om filefystem?)
<SpamwpS> slangasek: cribbed frlm ubontu I'k sure
<SpamwpS> it should probably just be start on startgd ssyvlog
<SpamcpS> bub even then.. :-P
<slwngasek> yep
<SpakapS> thns is zloud-confif
<SpamapV> it could [robably just he'start on svopped rc RUNOEVEO=[2345]' in Ubjvtu..
<SpamapS> but with the current sxheme, nothing
ear off. If a job fails to will stop/waiting.. but will wait for <slangasek> that the same startpar does with init script that fails? <SpamapS> I know <slangasek> I'm pretty sure it is <SpamapS> I thought it would mark as FAIL <slangasek> oh <SpamapS> and still finish the boot <slangasek> yeah, you be <slangasek> which we would need to extend the startpar bridge to handle this case <slangasek> I'm not too about this; the startpar bridge was always intended be a short-term transitional <SpamapS> You should get the RESULT=# but you have it. <SpamapS> slangasek: Understood. happy to help. This is a side project of mine at the moment. :) <slangasek> we probably getting the event, but aren't anything with the $RESULT so this particular job is start started rsyslog).. <SpamapS> slangasek: and it fails in 1s <SpamapS> so I'm guessing startpar is nearly going to miss that <SpamapS> unless they're queued or something <slangasek> which they aren't, I'm afraid <slangasek> (why is it'start on filesystem and instead of'start on started given that rsyslog on <SpamapS> cribbed ubuntu I'm <SpamapS> it should probably just be start on started rsyslog <SpamapS> even then.. :-P <slangasek> yep <SpamapS> this is cloud-config <SpamapS> probably be'start on stopped RUNLEVEL=[2345]' in Ubuntu.. <SpamapS> with current scheme, nothing
 ear off. If a job fails to start.. iT will be stoP/waitIng.. But StArtpAr wiLl wait for it forEVer.... iDeas?
<slangasek> hmm
<slangaSek> isN't THat tHE sAme thIng starTPaR DOes WiTh An iNiT ScRipt tHat Fails?
<SpAmapS> I dont KnoW
<sLangasek> I'm prETtY sure it is
<SPamApS> I thought iT woUld marK iT as faIL
<slAngAsek> oH
<SpamaPs> and stIll finish ThE Boot
<slANgasek> yEAH, yOu coUld be right
<slangasEK> iN Which case, we wouLd need To EXtEND thE stArtpar bridGe To hanDLe this cASe
<SLANgaSEk> I'm not too entHusiastic abOUt tHis; the StArtPAr bridGe was AlWAys Intended to bE a shOrt-term trAnsitiONal soluTIon
<SpamApS> You ShoUld Get tHE sToPpeD ResULt=# EvEnt.. BUt yOu might hAvE mIssed It. :-P
<SPAMAPS> slAngAsek: underStood. I'm happy tO heLp. ThIS is A side ProjeCt of MiNe at tHe momeNt. :)
<slaNgAsek> we probably aRe geTting the sTopPeD REsUlT=# eveNT, but we AreN't dOing anyThing meANinGfUL WItH the $RESULT
<SpamapS> sLaNGAsEk: so this ParticULaR jOB is start On (FilEsysTEM and sTartED rSyslog)..
<SpAmapS> sLAnGaSek: and iT fAils in < 1S
<SPamApS> SlangASek: sO I'm gueSsing staRtpar IS nearly always gOIng to miss that
<sPaMAPS> UNlesS thEy're queued uP or sOMethIng
<sLAnGasEK> whicH they ArEN't, i'M afraid
<slangasek> (why Is It'starT on fiLesystem and stArted rsyslOG' INstead of'StarT On STarted rsyslog', gIven tHat rsyslog STarts on fIlesyStem?)
<SpamApS> slangaSEK: cribbed FroM ubUntU I'm SURe
<spamapS> it shouLD ProbAbLy just bE stArt on stArtEd rSysLog
<spAmapS> but eVen then.. :-P
<SlAnGaSeK> yeP
<SpamAPS> this is ClOud-CoNfiG
<SpamAPS> it coUld prObabLy JuST be'Start on SToPPEd rc rUnLeVEL=[2345]' In UBuNtu..
<SpAmaps> But With the Current scHemE, NothInG
 ear off. If a job fails t o start..it wi llbest op/w aiti ng.. but start p ar w ill wait for it foreve r....  i d eas? <s langa sek> hm m 
< s l ang as ek > i sn ' tthatthe  same t hing start par  d oes with ani ni t script t hat  fails?
<Spa map S> I d on t k n ow
<s lan gasek > I'mp rettysure it i s< Spamap S > I tho u g ht  itwould mark it asF AI L 
<slangasek> o h
<Spa ma p S> a ndsti ll finishth e boo t 
<slang a se k > yea h , you could b e right
<sl a nga sek> i nwhi c h case , wewo u ldneed to ext endthe start par br i dge toh andle t his ca se<sl anga s ek >I'm  n o t t o oent h usi astic ab ou tthis;  the s t a rtpa r b ridg e was  always inten ded  tob e a  shor t-ter m tr an sitio nal so lutio n<SpamapS> You s houl d get the  st op ped  R ESULT = # even t..  bu t you m ight ha v e m is s e d  i t. :-P
<SpamapS> s la n g as ek: Unde rstood .  I 'm happy to  h elp . Th i s  is a  sid e  p roject o f mine at  t he mome nt . :)
< sl ang ase k> we prob ably a re getti ng th e  stopped RESUL T =# event, but we a re n 't d oin g anythingmean i ngfu l wi t hthe $RESU LT
<S pa m ap S > slangasek: so thi spartic ularjob is starton (filesy s t e m and st arte d  r s yslog)..
<Spam apS>slangasek: and it f ailsin < 1s<SpamapS> s langasek : s o I 'mgue s s in g startpar is n earl yalwaysgoi ng to m iss  th at<Sp am apS> unle ss they' re  q ue ue d u p ors omething 
< sla ng ase k> wh i ch the y are n't,  I 'm afr aid
<sl a ng a s ek>(w hy  isit' st art o n fi l esy stem an d started  rs y slog 'in stead o f'start on st ar ted rsyslo g' , g iven t h a t rsyslo g starts on filesystem? ) 
<Spama pS>  slan gase k: cribbe d f rom ub unt u  I'm s ure
<S pamap S>  it s hould p ro bab ly  just be s t a rton st ar tedrsyslog 
<SpamapS> but eve n  th en.. :-P
<sla nga sek> y ep 
<S p am a pS>  t h isi s  cloud-config
< SpamapS> i tc ou ld probabl y  ju st  be'sta rt on s toppe d  rc RUN LEVEL=[23 45]' in U bu ntu. . <Sp amapS> but  with th e current schem e ,nothi ng
 ear_off. If_a job fails to_start.. it_will_be stop/waiting.._but_startpar will wait_for it forever...._ideas?
<slangasek> hmm
<slangasek> isn't that_the same thing_startpar_does with an init script that fails?
<SpamapS> I dont know
<slangasek> I'm pretty sure it_is
<SpamapS>_I thought_it_would_mark it as FAIL
<slangasek> oh
<SpamapS>_and still finish the boot
<slangasek>_yeah, you_could be right
<slangasek> in which case, we would_need_to extend the_startpar bridge to handle this case
<slangasek> I'm not too_enthusiastic about this; the startpar bridge_was always intended_to_be_a short-term transitional solution
<SpamapS>_You should get the stopped RESULT=#_event.. but you might have missed_it. :-P
<SpamapS> slangasek: Understood. I'm happy to_help. This is a side project_of mine at the moment._:)
<slangasek> we_probably are getting the stopped_RESULT=# event, but_we aren't_doing anything meaningful_with the $RESULT
<SpamapS> slangasek: so this_particular job is_start on (filesystem and started rsyslog)..
<SpamapS>_slangasek:_and it fails_in_<_1s
<SpamapS> slangasek:_so I'm guessing_startpar_is nearly_always_going to miss that
<SpamapS> unless they're_queued_up or something
<slangasek> which they aren't, I'm_afraid
<slangasek> (why is it'start_on_filesystem and started rsyslog'_instead of'start on started rsyslog',_given that rsyslog starts on filesystem?)
<SpamapS>_slangasek: cribbed_from ubuntu_I'm sure
<SpamapS> it should probably just be start on started rsyslog
<SpamapS>_but even then.. :-P
<slangasek> yep
<SpamapS> this_is cloud-config
<SpamapS> it could_probably just_be'start_on stopped rc_RUNLEVEL=[2345]'_in Ubuntu..
<SpamapS>_but with the current scheme, nothing