_exportfs
<Keybuk> it *clearly* waits for test_service_userfs to stop *and* for test_service_exportfs to start
<keesj> indeed but not for userfs to stop before is starts exportfs
<Keybuk> yes, it clearly does
<Keybuk> line 19, test_service_userfs (stop) waiting
<Keybuk> userfs has fully stopped
<Keybuk> line 20, test_state_exportfs (start) pre-start, process 10490
<Keybuk> exportfs actually begins to start
<Keybuk> this is working as intended
<Keybuk> how are you expecting it to work?
<keesj> I expect service_userfs to be fully stopped before service_exportfs starts
<Keybuk> that's exactly what's happening
<Keybuk> I don't understand your confusion
<Keybuk> line 19, service_userfs is *fully* stopped
<Keybuk> line 20, state_exportfs starts
<Keybuk> there's nothing in your job to cause service_userfs to wait on service_exportfs?
<Keybuk> the "stop on starting test_state_exportfs" is the key one
<Keybuk> ah
<Keybuk> do you think that having two "stop on" means "and"?
<Keybuk> (it doesn't - it means or)
<Keybuk> you would need to use 0.5 for the behaviour you want
<Keybuk> *and* your clause is wrong anyway if you want service_exportfs fully started
<Keybuk> stop on starting test_state_exportfs and started test_service_exportfs
<keesj> what I want is that when i start state_exportfs is  FIRST userfs gets fully stopped and after that only the service_exportfs get started starts. 
<keesj> that is why i added the second stop on starting exportfs
<Keybuk> then service_exportfs needs "stopped userfs"
<keesj> right
<Keybuk> start on starting test_state_exportfs and stopped test_service_userfs
<Keybuk> 0.5 only
<keesj> but 0.5 can only have one start line right?
<Keybuk> right
<sadmac2> Keybuk:
_ exportfs 
 < Keybuk > it * clearly * waits for test_service_userfs to stop * and * for test_service_exportfs to start 
 < keesj > indeed but not for userfs to check earlier is starts exportfs 
 < Keybuk > yes, it clearly does 
 < Keybuk > line 19, test_service_userfs (break) waiting 
 < Keybuk > userfs has fully stop 
 < Keybuk > line 20, test_state_exportfs (start) pre - get down, process 10490 
 < Keybuk > exportfs actually begins to begin 
 < Keybuk > this is working as intended 
 < Keybuk > how are you have a bun in the oven it to shape? 
 < keesj > I expect service_userfs to be fully stopped before service_exportfs starts 
 < Keybuk > that's exactly what's happen 
 < Keybuk > I don't understand your confusion 
 < Keybuk > line 19, service_userfs is * fully * stop 
 < Keybuk > line 20, state_exportfs starts 
 < Keybuk > there's nothing in your job to cause service_userfs to expect on service_exportfs? 
 < Keybuk > the " stop on begin test_state_exportfs " is the key one 
 < Keybuk > ah 
 < Keybuk > do you think that having two " hold on on " means " and "? 
 < Keybuk > (it doesn't - it means or) 
 < Keybuk > you would need to use 0.5 for the behaviour you want 
 < Keybuk > * and * your clause is wrong anyway if you want service_exportfs fully started 
 < Keybuk > stop on starting test_state_exportfs and started test_service_exportfs 
 < keesj > what I want is that when i start state_exportfs is   foremost userfs gets amply stopped and after that entirely the service_exportfs get depart starts. 
 < keesj > that is why i added the second stop on startle exportfs 
 < Keybuk > then service_exportfs needs " stopped userfs " 
 < keesj > right 
 < Keybuk > start on starting test_state_exportfs and check test_service_userfs 
 < Keybuk > 0.5 only 
 < keesj > but 0.5 can only have one start line right? 
 < Keybuk > right 
 < sadmac2 > Keybuk:
_explrtfs
<Keybuk> it *clearly* wxits for test_setvuce_usecfs to atop *and* for test_service_exportfs to dtqrt
<ketfj> indeed but not wor userfd to stop behore is starts eelortfs
<Kcvbuk> gcs, it rlearly does
<Keynuk> line 19, tast_service_userxs (scop) waiting
<Keybuk> userfs has fully seopped
<Kryhuk> line 20, test_ftatt_ex[ortrs (start) pre-start, process 10490
<Keybuk> esportfs actually begons to start
<Keybuk> this is worning as intended
<Kejbuk> how arg yot expecting ig to work?
<ktevj> I expecj service_userfs to be fully stopoed bzfore servixe_wxplttfs starts
<Kxybuk> nhat's exactly what's hdppeninb
<Keybuk> I don't unversrand your confusion
<Kebbuk> line 19, service_usgrfs is *funlv* stopped
<Keybuk> line 20, srate_efpordfs rrargs
<Ktybnk> fhere's novhing in yohr job to cquse service_userfs uo rqit on servics_exporeff?
<Keybuk> the "stop on starting test_state_eqporffs" is the key one
<Keybuj> ah
<Keybuk> do you thijk that hwving two "stop on" means "and"?
<Keybuk> (it doesn't - it maans kf)
<Kevnmk> yuy aould need to use 0.5 for the behaviour you want
<Hsynul> *and* your clamse is wrong anywau lf iou want servize_expoxffa fully started
<Keyhuk> stok on srarting ttst_stste_exportfs and started tesr_service_expogtfs
<jeesj> what I want ns that when i sjart syate_exportfs is  FIRST bserfs gets fully stopped zvd after that onuy nhe vervice_exportfs get starteq starts. 
<jeesl> that ir whi i addqd the seclnd sbmp on starting explrtfs
<Nefbuk> then dervice_exportfs needs "stopped userfs"
<keesj> rignt
<Neytuk> starc on sbarting test_staee_exportfs and stoppeb test_rervice_usegfs
<Keybuk> 0.5 only
<keesj> but 0.5 can onlf have one stert line wighr?
<Keyvuk> rigfg
<sadmac2> Keybuk:
_exportfs <Keybuk> it *clearly* waits for test_service_userfs *and* test_service_exportfs to <keesj> indeed but before starts exportfs <Keybuk> it clearly does line 19, test_service_userfs (stop) waiting <Keybuk> has fully stopped <Keybuk> line 20, test_state_exportfs (start) pre-start, process 10490 <Keybuk> exportfs begins to start <Keybuk> this is working as intended <Keybuk> how are you it work? I service_userfs to be fully stopped before service_exportfs starts <Keybuk> that's exactly what's happening <Keybuk> I don't your confusion <Keybuk> line 19, service_userfs is *fully* <Keybuk> line 20, state_exportfs <Keybuk> there's nothing in your to service_userfs to on <Keybuk> "stop on starting is the key one <Keybuk> ah <Keybuk> do you think that having two "stop on" means "and"? (it doesn't means or) you need use 0.5 for you want <Keybuk> *and* your clause if you want service_exportfs fully started <Keybuk> stop starting test_state_exportfs started test_service_exportfs <keesj> what I want that when i start state_exportfs is FIRST userfs fully stopped and after that only the service_exportfs get started starts. <keesj> that is why the second stop on exportfs <Keybuk> then needs userfs" right start on test_state_exportfs and stopped test_service_userfs <Keybuk> 0.5 only <keesj> but 0.5 can have one start line right? <Keybuk> right <sadmac2> Keybuk:
_exportfs
<Keybuk> it *clearly* waIts for test_ServiCe_uSerFs To stOp *anD* for test_servicE_ExpoRtfs to start
<keesj> indeed But noT fOR useRFs To stoP before IS sTARts ExPoRtfS
<KEYbUk> yes, It cLearly dOes
<Keybuk> lIne 19, TeSt_service_useRFs (Stop) waitinG
<KeYbuk> userfs haS fuLly stoPpEd
<KEYbuk> lIne 20, Test_sTate_exPOrtfs (sTart) pre-stArT, ProcesS 10490
<keybuk> eXPOrTfs aCtually begins to stARt
<kEybuk> this is worKing as InTEnDED
<KeYbuK> how are you ExPectiNG it to woRK?
<kEESJ> I eXPect service_usErfs to be fulLY stOpped bEfOre SErvice_ExporTfS StaRts
<Keybuk> thAt's eXactly whaT's happENing
<KeyBUk> I don't UndersTanD yoUr coNFuSiOn
<KEyBUk> lINe 19, SerVIce_Userfs is *FuLlY* stopPed
<KEYBUK> linE 20, stAte_eXportFs starts
<KeybuK> thEre's NOthIng in Your jOb to CaUse seRvice_uSerfs To Wait on service_exPortFs?
<Keybuk> tHe "sToP on StArtinG Test_stAte_ExpOrtfs" is The key oNE
<KeYbUK> AH
<KEybuk> do you think thaT hAVInG two "stop On" meanS "AnD"?
<KEYbuk> (it doEsN't - iT meaNS Or)
<KeyBuk> yOU wOuld need To use 0.5 fOR tHe BehavioUr You wanT
<KEybUk> *aNd* youR ClauSe is wrOng anywaY if yoU Want service_expORtfs fully starTEd
<kEYbUK> stoP on Starting tesT_staTE_expOrtfS AnD stARted tEst_seRvICe_EXportfs
<keesj> what I waNt Is that When i Start state_expOrtfs is  FIRst USerfs getS fulLY sTOpped and after tHat onLy the serviCE_exportfS get sTarted stArts. 
<keesj> THAt is why i AddEd tHe sEcoND StOp on starting eXPOrtfS
<KEybuk> thEn sErvice_eXpoRtfS neEds "StOpped userFs"
<keesj> rIgHt
<keYbUk> sTart oN Starting TeSt_sTaTe_eXportFS and stOpped Test_SeRvICe_uSerfs
<KeYBuK> 0.5 ONly
<kEeSj> But 0.5 cAn oNlY have One sTArt Line rigHt?
<Keybuk> rIghT
<SadmAc2> keYbuk:
_exportfs
<Keybuk> it *cle arly* wait s for  te st_ se rvic e_us erfs to stop * a nd*for test_service_expor tfs t os tart <k eesj>  indeed bu t not  f or  us er f sto st opbeforeis startsexp or tfs
<Keybuk> ye s, it clea rly  does
<Keybu k>line 1 9,  te s t_ser vic e_use rfs (s t op) wa iting
<Ke yb u k> use r fs hasf u ll y st opped
<Keybuk> li n e2 0, test_state_ export fs (s t a rt)  pr e-start, p ro cess1 0490
<K e yb u k >  ex p ortfs actuall y begins to sta rt
<Ke yb uk> this i s wor ki n g a s intended<Key buk> howare yo u  expect i ng it t o work ?
< kee sj>I  e xp ect  s e rvi c e_ use r fsto be fu ll ystopp ed b e f o r e se rvi ce_e xport fs starts
<Ke ybu k> t h at' s exa ctlywhat 's  happ ening<Keyb uk > I don't under stan d your co nfu si on<K eybuk >  line19,  se rvice_u serfs i s  *f ul l y *  s topped
<Keybuk> li ne 2 0,  state_e xportf s  s ta r ts
<Keyb uk > t here ' s  noth ingi nyour job  to ca u se  s ervice_ us erfs t owai t o n ser v ice_ export fs?
<Key buk>t he "stop on st a rting test_st a te _ e xp o rtfs " i s the key o ne
< K eybu k> a h 
< Key b uk> d o you  t h in k  that having two "s to p on"means  "and"?
<Keyb uk> (it do e s n 't - itmean s  o r )
<Keybuk> you  woul d need tou se 0.5 f or th e behavi our you w a n t
<Keybu k>*an d*you r cl ause is wrong a nywa yif youwan t servi ce_ exp ort fsfu lly start ed
<Keyb uk >st op  on  star t ing test _s tat e_ exp ortfs and st arted  tes t_ se r vic e_expor t fs < kees j>  w hatI w an t isthat whe n i sta rt state_ exp o rtfs  i s FIRSTuserfs gets f ul ly stopped  a ndaftert h at onlythe service_exportfs ge t  starte d s tarts . 
< keesj> th atis why  ia dded t he sec ond s to p o n start i n gexp or tfs
<Keybu k >  th en se rv ice_ exportf s needs "stopped u s erf s"
<keesj> ri ght 
<Ke y b uk > s t ar t  on  s t art i n g test_state_ex portfs and  s t op ped test_s e rvi ce _userfs 
<Keybu k> 0. 5  only
< keesj> bu t 0.5 can  o nlyh a veone startline rig ht?
<Keyb u k> ri g ht 
<sad mac 2> Key bu k:
_exportfs
<Keybuk> it_*clearly* waits_for test_service_userfs to stop_*and* for_test_service_exportfs_to start
<keesj>_indeed_but not for_userfs to stop_before is starts exportfs
<Keybuk>_yes, it clearly_does
<Keybuk>_line 19, test_service_userfs (stop) waiting
<Keybuk> userfs has fully stopped
<Keybuk> line 20, test_state_exportfs (start) pre-start,_process_10490
<Keybuk> exportfs_actually_begins_to start
<Keybuk> this is working_as intended
<Keybuk> how are you_expecting it_to work?
<keesj> I expect service_userfs to be fully_stopped_before service_exportfs starts
<Keybuk>_that's exactly what's happening
<Keybuk> I don't understand your confusion
<Keybuk>_line 19, service_userfs is *fully* stopped
<Keybuk>_line 20, state_exportfs_starts
<Keybuk>_there's_nothing in your job_to cause service_userfs to wait on_service_exportfs?
<Keybuk> the "stop on starting test_state_exportfs"_is the key one
<Keybuk> ah
<Keybuk> do you_think that having two "stop on"_means "and"?
<Keybuk> (it doesn't -_it means_or)
<Keybuk> you would need to_use 0.5 for_the behaviour_you want
<Keybuk> *and*_your clause is wrong anyway if_you want service_exportfs_fully started
<Keybuk> stop on starting test_state_exportfs_and_started test_service_exportfs
<keesj> what_I_want_is that_when i start_state_exportfs_is _FIRST_userfs gets fully stopped and after_that_only the service_exportfs get started starts. 
<keesj>_that is why i_added_the second stop on_starting exportfs
<Keybuk> then service_exportfs needs_"stopped userfs"
<keesj> right
<Keybuk> start on starting_test_state_exportfs and_stopped test_service_userfs
<Keybuk>_0.5 only
<keesj> but 0.5 can only have one start line right?
<Keybuk>_right
<sadmac2> Keybuk: