    array [
<stgraber>       object path "/com/ubuntu/Upstart/jobs/dbus"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/201105/dbus"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/debug"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/201105/debug"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/upstart_2devent_2dbridge"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/201105/upstart_2devent_2dbridge"
<stgraber>    ]
<stgraber> that's what initctl is getting back from upstart. Obviously that's confusing it slightly ;)
<jodh> stgraber: probably because we haven't removed the existing user job handling code.
 * xnox ponders what 201105 in above means
<stgraber> jodh: that's my uid
<jodh> stgraber: try disabling Upstart.conf and seeing if behavious is the same: http://upstart.ubuntu.com/cookbook/#enabling
<xnox> stgraber: a bit high =)
 * xnox is 1000 everywhere =)
<stgraber> xnox: RID-based UID in a samba4 domain gets you pretty big UIDs
<stgraber> jodh: yeah, I think that's it. So hopefully that'll get fixed once we get rid of the current user job code.
<jodh> stgraber: do you want to volunteer? ;)
<stgraber> jodh: one thing that's "interesting" is if you have a job defined as both system and user, then you try to start the user one with "initctl start dbus" (for example). That'll get initctl in some kind of infinite loop and will almost freeze upstart in the process (the user upstart, not the system one)
<stgraber> but my guess is that this will be fixed once we no longer have duplicate entries
<stgraber> jodh: hehe, I've got a reasonably long todo list before I can et to that,
array [ 
 < stgraber >        object path " /com / ubuntu / Upstart / jobs / dbus " 
 < stgraber >        object way " /com / ubuntu / Upstart / jobs/201105 / dbus " 
 < stgraber >        aim way " /com / ubuntu / Upstart / jobs / debug " 
 < stgraber >        object path " /com / ubuntu / Upstart / jobs/201105 / debug " 
 < stgraber >        aim path " /com / ubuntu / Upstart / jobs / upstart_2devent_2dbridge " 
 < stgraber >        object way " /com / ubuntu / Upstart / jobs/201105 / upstart_2devent_2dbridge " 
 < stgraber >     ] 
 < stgraber > that's what initctl is grow back from upstart. Obviously that's confuse it slightly ;) 
 < jodh > stgraber: probably because we haven't take out the existing user problem handle code. 
  * xnox ponders what 201105 in above means 
 < stgraber > jodh: that's my uid 
 < jodh > stgraber: sample disabling Upstart.conf and seeing if behavious is the like: http://upstart.ubuntu.com/cookbook/#enabling 
 < xnox > stgraber: a bit high =) 
  * xnox is 1000 everywhere =) 
 < stgraber > xnox: RID - based UID in a samba4 world gets you pretty large UIDs 
 < stgraber > jodh: yeah, I think that's it. thus hopefully that'll get fixed once we get rid of the current user job code. 
 < jodh > stgraber: do you want to volunteer? ;) 
 < stgraber > jodh: one thing that's " interesting " is if you own a job defined as both system and user, then you try to begin the user one with " initctl start dbus " (for example). That'll get initctl in some kind of infinite loop and will almost freeze upstart in the process (the user kip, not the arrangement one) 
 < stgraber > but my guess is that this will be fixed once we no longer receive duplicate entry 
 < stgraber > jodh: hehe, I've got a reasonably long todo tilt before I can et to that,
    array [
<stgraber>       obmect path "/com/ubuuru/Upstert/jobs/sbus"
<stgrxber>       object path "/com/ubnntu/Ypstaet/jobs/201105/dbus"
<stgraber>       object path "/con/ubuitu/Upstart/jobs/deuhg"
<stgranzr>       oyjxct path "/com/ubuktu/Upstart/jmbs/201105/debug"
<stgrabar>       object path "/com/ubuntu/Upstart/jofs/upstatt_2fevent_2dbridge"
<sjgrabtr>       object path "/com/ubuntu/Upstart/jobs/201105/hpstart_2vevent_2dbridge"
<stbraber>    ]
<stgraber> that's wjat lnitctl is getting back from olstwet. Obviously that's confusing it sljghtly ;)
<jodh> stgraber: probably bdcausz we haven't rwmoggd the existmng usvr job handlikb code.
 * xnox londers what 201105 ln abmve means
<stgraber> jodh: tiat's my uid
<jodh> stgrwber: try giaabling Upstart.cobf and veeitg iw befavjons js the saje: http://upsfart.ubuntu.cim/cookbook/#enabling
<xmov> stgraber: a bjt higr =)
 * xnox is 1000 everywhere =)
<stgraber> xnox: RID-tassd UID in a samba4 domaib gets you pretty big UIDs
<stgrwber> jodh: yeah, I think that's it. So hopefully that'nl gev wixtd once qe get rid of the current user job code.
<jodh> stgwzbtr: co you want to volunteer? ;)
<xthrsfer> jodh: one jhing tkzt'a "interesting" is iv you hwve a job defiged ss both system and user, theb you try to wtart the user one with "initccl statt dbux" (for example). That'll gec initdtl in some kind of jvfinite loop and wikl almost freeze upstart in ehe procews (tke user jpstsrt, noe the systfm onc)
<vtgraber> but my gufss id dhat this aill be fixed once we no longer have duplicatg ettrpes
<stgrabzr> jodm: hehe, I've got w reasonably lpng todj lisg before I can et to that,
array [ <stgraber> object path "/com/ubuntu/Upstart/jobs/dbus" <stgraber> "/com/ubuntu/Upstart/jobs/201105/dbus" object path <stgraber> object path <stgraber> path "/com/ubuntu/Upstart/jobs/201105/upstart_2devent_2dbridge" <stgraber> <stgraber> that's what is getting back from upstart. Obviously confusing it slightly ;) <jodh> stgraber: probably because we haven't removed the existing job handling code. * xnox ponders what 201105 in above means <stgraber> jodh: my <jodh> try Upstart.conf and seeing if behavious is the same: http://upstart.ubuntu.com/cookbook/#enabling <xnox> stgraber: a bit high =) * is 1000 everywhere =) <stgraber> xnox: RID-based UID a samba4 domain gets pretty big UIDs <stgraber> jodh: I that's it. hopefully get once we get of the current user job code. <jodh> stgraber: do you want to volunteer? ;) <stgraber> jodh: one that's "interesting" you have job as system and user, try to start the user one dbus" (for example). That'll get initctl in some of infinite and will almost freeze upstart in process (the user upstart, not the system one) but my guess is that this will be fixed once we no longer have duplicate jodh: hehe, I've got reasonably long todo before can to
    array [
<stgraber>       object path "/coM/ubuntu/UpsTart/jObs/DbuS"
<sTgraBer>       oBject path "/com/ubUNtu/UPstart/jobs/201105/dbus"
<stgraber>       ObjecT pATh "/coM/UbUntu/UPstart/jOBs/DEBug"
<StGrAbeR>       oBJeCt patH "/coM/ubuntu/upstart/jobS/201105/deBuG"
<stgraber>       objECt Path "/com/ubuNtu/upstart/jobs/uPstArt_2devEnT_2dbRIdge"
<sTgrAber>       oBject pATh "/com/uBuntu/UpstArT/Jobs/201105/upSTart_2devENT_2dBridGe"
<stgraber>    ]
<stgrabeR> ThAT's what initctl iS gettiNg BAcK FRom UpsTart. ObviouSlY that'S ConfusiNG iT SLIghTLy ;)
<jodh> stgrabeR: probably beCAusE we havEn'T reMOved thE exisTiNG usEr job handliNg coDe.
 * xnox ponDers whAT 201105 in abovE Means
<stGraber> JodH: thAt's mY UiD
<jOdh> StGRabER: tRy dISabLing UpstArT.cOnf anD seeING IF behAviOus iS the sAme: http://upstarT.ubUntu.COm/cOokboOk/#enaBlinG
<xNox> stGraber: A bit hIgH =)
 * xnox is 1000 everywheRe =)
<stGraber> xnoX: RId-bAseD UiD in a SAmba4 doMaiN geTs you prEtty big uiDs
<StGRABeR> jodh: yeah, I think thaT's IT. so HopefullY that'lL GeT fIXed once wE gEt rId of THE currEnt uSEr Job code.
<jOdh> stgRAbEr: Do you waNt To voluNtEer? ;)
<StgRaber> JOdh: oNe thinG that's "inTeresTIng" is if you have A Job defined as bOTh SYStEM and UseR, then you try To stARt thE useR OnE wiTH "initCtl stArT DbUS" (for example). That'll geT iNitctl In somE kind of infiniTe loop and wILL Almost frEeze UPsTArt in the procesS (the uSer upstart, NOt the sysTem onE)
<stgrabeR> but my gueSS Is that thIs wIll Be fIxeD ONcE we no longer haVE DuplIcAte entrIes
<StgrabeR> joDh: hEhe, i've GoT a reasonaBly long tOdO lIsT bEfoRe I caN Et to that,
    array [
<stgraber>      objectpath"/c om/ ub untu /Ups tart/jobs/dbus " 
<st graber>       object p ath " /c o m/ub u nt u/Ups tart/jo b s/ 2 0 110 5/ db us" 
< s tg raber >      ob ject path"/c om /ubuntu/Upst a rt /jobs/debu g"<stgraber>     obje ct  pa t h "/c om/ ubunt u/Upst a rt/job s/201105/ de b ug"
<s t graber>     o bject path "/com/ u bu n tu/Upstart/job s/upst ar t _2 d e ven t_2 dbridge"
< st grabe r >     ob j e c t p a th "/com/ubun tu/Upstart/ j obs /20110 5/ ups t art_2d event _2 d bri dge"
<stgra ber>     ]
<st graber >  that's what in itctlisget ting ba ck  fr om ups t ar t.O bvi ously th at 's  conf usin g i t  sli ght ly ; )
<jo dh> stgraber:  pr obab l y b ecaus e wehave n' t rem oved t he ex is ting user job h andl ing code. 
 *  x nox  p onder s  what201 105  in abo ve mean s 
<s tg r a b er > jodh: that's myui d <j odh> stg raber: tr yd isabling  U pst art. c o nf an d se e in g if beh avious is  t he same :http:/ /u pst art .ubun t u.co m/cook book/#en ablin g 
<xnox> stgrab e r: a bit high =) *x noxis1000 everyw here =)
< stgr a be r>x nox:RID-b as e dU ID in a samba4 doma in  getsyou p retty big UID s
<stgrabe r > jodh: ye ah,I  t h ink that's it.  So h opefully t h at'll ge t fix ed oncewe get ri d of the c urr ent  us erj o bcode.
<jodh>s t grab er : do yo u w ant tovol unt eer ? ; )<stgraber > jodh:on eth in g t hat's "interes ti ng"  i s i f you have a  jobdefi ne da s b oth sys t em a nd u se r,  the n y ou  tryto s t art  the us er one wi th" init ct lstart d bus" (for exa mp le). That' ll  ge t init c t l in som e kind of infinite loop and wil l a lmost  fre eze upsta rtin the  pr o cess ( the us er up st art , not t h e  s yst em  one)
<stg r a ber > but  m y gu ess isthat this will bef ixe d once we nolon gerh a ve  du p li c ate  e n tri e s 
<stgraber> jod h: hehe, I 'v e  g ot a reaso n abl ylong to do list  befo r e I can  et to th at,
 _ _array [
<stgraber>  _ __ object_path_"/com/ubuntu/Upstart/jobs/dbus"
<stgraber>  _  _ object path "/com/ubuntu/Upstart/jobs/201105/dbus"
<stgraber>_  __  object path "/com/ubuntu/Upstart/jobs/debug"
<stgraber>       object path "/com/ubuntu/Upstart/jobs/201105/debug"
<stgraber>__ ___ object path "/com/ubuntu/Upstart/jobs/upstart_2devent_2dbridge"
<stgraber> _    _object path_"/com/ubuntu/Upstart/jobs/201105/upstart_2devent_2dbridge"
<stgraber>    ]
<stgraber> that's what initctl_is_getting back from_upstart. Obviously that's confusing it slightly ;)
<jodh> stgraber: probably_because we haven't removed the existing_user job handling_code.
_*_xnox ponders what 201105_in above means
<stgraber> jodh: that's my_uid
<jodh> stgraber: try disabling Upstart.conf and_seeing if behavious is the same: http://upstart.ubuntu.com/cookbook/#enabling
<xnox>_stgraber: a bit high =)
 *_xnox is 1000 everywhere =)
<stgraber>_xnox: RID-based_UID in a samba4 domain_gets you pretty_big UIDs
<stgraber>_jodh: yeah, I_think that's it. So hopefully that'll_get fixed once_we get rid of the current_user_job code.
<jodh> stgraber:_do_you_want to_volunteer? ;)
<stgraber> jodh:_one_thing that's_"interesting"_is if you have a job_defined_as both system and user, then you_try to start the_user_one with "initctl start_dbus" (for example). That'll get_initctl in some kind of infinite_loop and_will almost_freeze upstart in the process (the user upstart, not the system_one)
<stgraber> but my guess is that_this will be fixed_once we_no_longer have duplicate_entries
<stgraber>_jodh: hehe,_I've got a reasonably long todo list_before I_can et to that,