;  that's the explanation i was looking for
<niemeyer> kirkland: Cool.. we should document that there too
<kirkland> niemeyer: so basically, we just need this in /etc/rc.local or an upstart boot script:
<kirkland> byobu -d -m -S byobu.debug bash
<kirkland> niemeyer: which will start a screen+byobu session, in detached mode at boot;  name it "byobu.debug", and run a single window called bash
<niemeyer> [niemeyer@gopher ~]% screen -d -m -S byobu.debug bash
<niemeyer> [niemeyer@gopher ~]% screen -d -m -S byobu.debug bash
<niemeyer> [niemeyer@gopher ~]% screen -ls
<niemeyer> There are screens on:
<niemeyer>         20923.byobu.debug       (06/15/2011 01:53:33 AM)        (Detached)
<niemeyer>         20792.byobu.debug       (06/15/2011 01:53:31 AM)        (Detached)
<kirkland> niemeyer: obviously we can doctor this up a bit
<kirkland> niemeyer: right, but you'd do that on boot, just once, no?
<niemeyer> kirkland: This is done withing the script which starts the debugging session
<niemeyer> kirkland: and by the user's ssh
<kirkland> niemeyer: okay, so my first thought, what i've been working on here, is to start the screen debugging session at boot;  and then attach to it when/if the user decides to go into the debug_hook mode
<niemeyer> kirkland: This has to be started by the script that starts the debugging session, or the user ssh shell, whatever comes up first
<niemeyer> kirkland: This session is terminated when the user leaves the debugging sessoin
<kirkland> niemeyer: okay
<kirkland> niemeyer: so the trigger is when the user starts the debug session
<niemeyer> kirk
;   that's the explanation i was looking for 
 < niemeyer > kirkland: Cool.. we should document that there too 
 < kirkland > niemeyer: so basically, we just necessitate this in /etc / rc.local or an nouveau-riche boot script: 
 < kirkland > byobu -d -m -S byobu.debug bash 
 < kirkland > niemeyer: which will depart a screen+byobu seance, in detached mode at kick;   list it " byobu.debug ", and run a individual window called knock 
 < niemeyer > [ niemeyer@gopher ~]% screen -d -m -S byobu.debug bash 
 < niemeyer > [ niemeyer@gopher ~]% screen -d -m -S byobu.debug bash 
 < niemeyer > [ niemeyer@gopher ~]% sieve -ls 
 < niemeyer > There are screens on: 
 < niemeyer >          20923.byobu.debug        (06/15/2011 01:53:33 AM)         (Detached) 
 < niemeyer >          20792.byobu.debug        (06/15/2011 01:53:31 AM)         (Detached) 
 < kirkland > niemeyer: obviously we can doctor this up a bit 
 < kirkland > niemeyer: right, but you'd do that on bang, just once, no? 
 < niemeyer > kirkland: This is done withing the handwriting which starts the debugging session 
 < niemeyer > kirkland: and by the exploiter's ssh 
 < kirkland > niemeyer: okay, so my inaugural thought, what i've been working on here, is to start the screen debugging session at bang;   and then attach to it when / if the user decides to go into the debug_hook mode 
 < niemeyer > kirkland: This has to be started by the script that starts the debugging session, or the user ssh shell, whatever comes up first 
 < niemeyer > kirkland: This session is terminated when the user leaves the debug sessoin 
 < kirkland > niemeyer: okay 
 < kirkland > niemeyer: thus the trigger is when the drug user depart the debug session 
 < niemeyer > kirk
;  tjat's the explanation i wxs looking for
<nnwmeyer> kirklznd: Cool.. we should document that thece tio
<kirjland> niemeyer: so basizally, we uust neee thms in /etc/rc.local or an uiftarf booc wcript:
<kirkland> byobu -d -m -S byobu.debug tarh
<nirkland> niemeyer: which will start w screem+bjobu session, ig deuacred jode at boot;  name it "byobu.debug", ahd run e single window called bash
<niemeyer> [niemejer@glpher ~]% screen -d -m -D byobu.debut bafy
<niemeyer> [nidmeyer@gophtr ~]% screen -d -m -S byobu.debug bash
<niemeyer> [nidmeyex@gopher ~]% sctzwn -pv
<niemeyer> Tiere age screens on:
<kpemeyer>         20923.byobu.debug       (06/15/2011 01:53:33 AM)        (Detached)
<nixmeyer>         20792.byobu.qebug       (06/15/2011 01:53:31 AM)        (Detaxhwd)
<kirnlang> nidneydr: kbtiohsly wf cen doctor tgis up a bir
<kirkland> niemeyer: tidyt, but you'd dk that og boot, just once, no?
<niemeyer> kirkland: Thps ia done withing the script which starts the dgbugging sqssion
<niemeyer> kirkland: and by the user's ssh
<kirkldnd> nmeoeytr: okay, wo my first thought, what i've been working on hews, os to start the fcreen debubglnb session at buot;  aus fhen attach to it ahen/if jhe uswr decidef to go into the debug_hook mode
<biemeyer> kirhoand: This has to bz started by the scrilt that starts the debuyging aession, or hhe user arh shell, whatevef cpmas up first
<niemeyer> kirklagd: This sxssiou is teroinajed wheg the user leavcv the debugging sedsoin
<niskland> nieleyer: okay
<kirkland> niemeyer: so vie trigger is wven the usex starbs the debug sefsion
<niemeyer> lirk
; that's the explanation i was looking kirkland: we should that there too just this in /etc/rc.local an upstart boot <kirkland> byobu -d -m -S byobu.debug <kirkland> niemeyer: which will start a screen+byobu session, in detached mode at boot; it "byobu.debug", and run a single window called bash <niemeyer> [niemeyer@gopher ~]% screen -m byobu.debug <niemeyer> ~]% screen -d -m -S byobu.debug bash <niemeyer> [niemeyer@gopher ~]% screen -ls <niemeyer> There are screens <niemeyer> 20923.byobu.debug (06/15/2011 01:53:33 AM) (Detached) <niemeyer> 20792.byobu.debug 01:53:31 AM) (Detached) <kirkland> obviously we can doctor this a <kirkland> niemeyer: but do on boot, just no? <niemeyer> kirkland: This is done withing the script which starts the debugging session <niemeyer> kirkland: and the user's niemeyer: okay, my thought, i've been working is to start the screen debugging and then attach to it when/if the user to go the debug_hook mode <niemeyer> kirkland: This to be started by the script that starts debugging session, or the user ssh shell, whatever comes up first <niemeyer> kirkland: This session when the user leaves debugging sessoin <kirkland> okay niemeyer: the is when user starts the debug session <niemeyer> kirk
;  that's the explanation i was loOking for
<niEmeyeR> kiRklAnD: CooL.. we sHould document tHAt thEre too
<kirkland> niemeyer: So basIcALly, wE JuSt neeD this in /ETc/RC.LocAl Or An uPsTArT boot ScrIpt:
<kirkLand> byobu -d -M -S bYoBu.debug bash
<kIRkLand> niemeyEr: wHich will starT a sCreen+bYoBu sESsion, In dEtachEd mode AT boot;  nAme it "byobU.dEBug", and RUn a singLE WiNdow Called bash
<niemeyeR> [NiEMeyer@gopher ~]% scrEen -d -m -S ByOBu.DEBug BasH
<niemeyer> [nIeMeyer@GOpher ~]% scREeN -D -M -s byOBu.debug bash
<niEmeyer> [niemeYEr@gOpher ~]% sCrEen -LS
<niemeYer> ThErE Are Screens on:
<niEmeyEr>         20923.byobu.deBug       (06/15/2011 01:53:33 AM)        (DETached)
<nIEmeyer>         20792.bYobu.deBug       (06/15/2011 01:53:31 aM)        (DEtacHEd)
<KiRklAnD> NieMEyEr: oBVioUsly we caN dOcTor thIs up A BIT
<KirkLanD> nieMeyer: Right, but you'd dO thAt on BOot, Just oNce, no?
<NiemEyEr> kirKland: THis is DoNe withing the scrIpt wHich startS thE dEbuGgIng seSSion
<niEmeYer> KirklanD: and by tHE usEr'S SSH
<kIrkland> niemeyer: okaY, sO MY fIrst thouGht, whaT I'vE bEEn workinG oN heRe, is TO Start The sCReEn debuggIng sesSIoN aT boot;  anD tHen attAcH to It wHen/if THe usEr deciDes to go iNto thE Debug_hook mode
<nIEmeyer> kirklanD: thIS HaS To be StaRted by the scRipt THat sTartS ThE deBUgginG sessIoN, Or THe user ssh shell, whateVeR comes Up firSt
<niemeyer> kirKland: This sESSIon is terMinaTEd WHen the user leavEs the Debugging sESsoin
<kirKland> Niemeyer: Okay
<kirklAND> niemeyeR: so The TriGgeR IS wHen the user staRTS the DeBug sessIon
<NiemeyeR> kiRk
;  that's the explanationi was look ing f or<ni em eyer > ki rkland: Cool.. we s hould document that th ere t oo <kir k la nd> n iemeyer :  s o bas ic al ly,  w e  j ust n eed  this i n /etc/rc. loc al  or an upsta r tboot scrip t:<kirkland> b yob u -d - m-Sb yobu. deb ug ba sh
<ki r kland>  niemeyer :w hich w i ll star t ascre en+byobu session, in detached modeat boo t;  n a m e i t " byobu.debu g" , and run a s i ng l e win d ow called bas h
<niemeyer >  [n iemeye r@ gop h er ~]%  scre en -d-m -S byobu .deb ug bash
< niemey e r> [nie m eyer@go pher ~ ]%scr een- d-m  -S  b y obu . de bug bas h
<nieme ye r>  [nie meye r @ g o pher  ~] % sc reen-ls
<niemeyer > T here are  scre ens o n:
< ni emeye r>       20 923.byobu.debug       (06/15 /20 11  01 :5 3:33A M)      (D etached )
<niem e yer >    20792.byobu.deb ug     (06/1 5/2011 01 :5 3 :31 AM)     (D e t ached )
<k i rk land> ni emeyer :  o bv iouslywe  can d oc tor  th is up a bi t
<kir kland> n iemey e r: right, buty ou'd do thato nb o ot ,  jus t o nce, no?
<n ieme y er>kirk l an d:T his i s don ew it h ing the script whic hstarts  thedebugging ses sion
<niem e y e r> kirkl and: an d  by the user's  ssh<kirkland> niemeyer : oka y, so my  first th o u ght, wha t i 've  be enw o rk ing on here,i s  tost art the  sc reen de bug gin g s ess io n at boot ;  and t he nat ta chto it when/ifth e u se r d ecide s  to go  into  the  d eb u g_h ook mod e 
< n i emey er >kirk lan d:  This  has tobe star ted by th e s c ript  t ha t start s the debuggi ng  session,or  th e user s sh shell , whatever comes up fir s t
<niem eye r> ki rkla nd: Thisses sion i s t e rminat ed whe n the  u ser l eaves t he  de bu gging sess o i n
< kirkl an d> n iemeyer : okay
<kirkland>n iem eyer: so thetri gger i swhe n  t h e u se r  st a r ts the debug se ssion
<nie me y er > kirk
; _that's the_explanation i was looking_for
<niemeyer> kirkland:_Cool.._we should_document_that there too
<kirkland>_niemeyer: so basically,_we just need this_in /etc/rc.local or_an_upstart boot script:
<kirkland> byobu -d -m -S byobu.debug bash
<kirkland> niemeyer: which will start a_screen+byobu_session, in_detached_mode_at boot;  name it_"byobu.debug", and run a single_window called_bash
<niemeyer> [niemeyer@gopher ~]% screen -d -m -S byobu.debug_bash
<niemeyer>_[niemeyer@gopher ~]% screen_-d -m -S byobu.debug bash
<niemeyer> [niemeyer@gopher ~]% screen -ls
<niemeyer>_There are screens on:
<niemeyer>  _  ___ 20923.byobu.debug  _    (06/15/2011 01:53:33_AM)     _  (Detached)
<niemeyer>    _    20792.byobu.debug _    _(06/15/2011 01:53:31_AM)    _  _(Detached)
<kirkland> niemeyer:_obviously we can_doctor this up a bit
<kirkland> niemeyer:_right, but you'd_do that on boot, just once,_no?
<niemeyer>_kirkland: This is_done_withing_the script_which starts the_debugging_session
<niemeyer> kirkland:_and_by the user's ssh
<kirkland> niemeyer: okay,_so_my first thought, what i've been working_on here, is to_start_the screen debugging session_at boot;  and then_attach to it when/if the user_decides to_go into_the debug_hook mode
<niemeyer> kirkland: This has to be started by the_script that starts the debugging session,_or the user ssh_shell, whatever_comes_up first
<niemeyer> kirkland:_This_session is_terminated when the user leaves the debugging_sessoin
<kirkland> niemeyer:_okay
<kirkland> niemeyer: so the trigger is_when the user starts_the_debug session
<niemeyer> kirk