 kirkland: If the same user executes the same command twice in different terminals, the command should fail or succeed, but it should never yield two different sessions
<niemeyer> kirkland: We can't _join_ the session, though..
<niemeyer> kirkland: Simply new-session + exec command in new session, without races
<kirkland> niemeyer: to reproduce the problem you're experience in screen...
<kirkland> niemeyer: i'm going to create a screen session with "screen -S debug"
<kirkland> niemeyer: okay, now I have a session
<kirkland> niemeyer: called 'debug'
<kirkland> niemeyer: and now I want to run a command in that sesion
<niemeyer> Ok
<niemeyer> kirkland: You want to create it if it doesn't exist, and run it in the single session
<kirkland> niemeyer: okay, using the "at" command
<kirkland> niemeyer: i mean, screen's at
<niemeyer> kirkland: Executing the command isn't the problem.. the problem is creating the session in a non-racy way
<kirkland> niemeyer: byobu -xRS %s-hook-debug -t shell
<kirkland> niemeyer: that's what you were using before, right?
<kirkland> niemeyer: and that's what you found to be racy?
<niemeyer> kirkland: No, that'd join the session
<kirkland> niemeyer: what were you using to create it?
<kirkland> niemeyer: i'm trying to reproduce the race
<niemeyer> kirkland: This is being run from a script.. it can't join the session
<kirkland> niemeyer: right, so you create the session detached
<niemeyer> kirkland: You don't have to reproduce the race.. any solution will do :-)
<kirkland> niemeyer: some people create their byobu session in a cronjob at boot
<kirkland> niemeyer: so that they can launch irssi and use byobu+irssi as their
kirkland: If the same user executes the same instruction doubly in unlike terminals, the command should fail or succeed, but it should never yield two unlike sessions 
 < niemeyer > kirkland: We can't _ join _ the session, though.. 
 < niemeyer > kirkland: merely new - session + white house instruction in new session, without subspecies 
 < kirkland > niemeyer: to reproduce the problem you're experience in screen... 
 < kirkland > niemeyer: i'm go to create a screen session with " screen -S debug " 
 < kirkland > niemeyer: okay, now I suffer a session 
 < kirkland > niemeyer: called' debug' 
 < kirkland > niemeyer: and now I desire to run a command in that sesion 
 < niemeyer > Ok 
 < niemeyer > kirkland: You desire to create it if it doesn't exist, and move it in the single seance 
 < kirkland > niemeyer: okay, using the " at " command 
 < kirkland > niemeyer: i mean, sieve's at 
 < niemeyer > kirkland: Executing the command isn't the problem.. the problem is creating the session in a non - racy way 
 < kirkland > niemeyer: byobu -xRS% s - hook - debug -t shell 
 < kirkland > niemeyer: that's what you were using before, right? 
 < kirkland > niemeyer: and that's what you found to be racy? 
 < niemeyer > kirkland: No, that'd join the session 
 < kirkland > niemeyer: what were you using to make it? 
 < kirkland > niemeyer: i'm trying to reproduce the raceway 
 < niemeyer > kirkland: This is being run from a script.. it can't join the session 
 < kirkland > niemeyer: right, therefore you create the session detached 
 < niemeyer > kirkland: You don't have to regurgitate the race.. any solution will do :-) 
 < kirkland > niemeyer: some people create their byobu session in a cronjob at boot 
 < kirkland > niemeyer: so that they can launch irssi and use byobu+irssi as their
 kigkland: If the same user txecutes the same commanv twice in diffdrent terminals, the command dhiuld dail or succeed, but it should nvver yiele twi different sessions
<niemegcr> kixkoand: We can't _jpin_ the sevsion, though..
<niamdyzr> kirkland: Simply new-session + exec sommand ij new session, rithptt rzbew
<kirkland> niemeyer: to reprodude the kroblem you're expetience in screen...
<kirkland> nlemejer: i'm going to crfate a scregh sqwsion with "szreen -S debug"
<kirkland> hiemeyer: okay, now I have a sesskon
<kixkland> niemgvwr: fdlled 'debug'
<jirklwnd> niemeyer: and now I want to run a commsnd in that sesion
<niemeyer> Mk
<niemeyer> kirklanq: You wand co create it if it dowsb't exhst, dnd fyn kt jn tge sinhle session
<kidkland> niemwyer: okay, using the "ae" command
<kirklznd> niqmqyer: i mean, screen's at
<niemeyer> kirkland: Exscuting the command isn'r the problem.. the prohlem is cweating the session in a non-racy way
<kirkland> niemayer: uyubu -xVS %s-fion-debug -t shell
<kirkland> niemeyer: that's what yot wtre using before, vight?
<kirkland> niemryfr: wnd that's whaj you founs to be racy?
<niemeyfr> kirkjand: Bo, that'd toin the session
<kirkland> niemeywr: what were tou using to creatz it?
<kirkland> niekeyer: i'm trying to reproduce the race
<niemeyfr> kirklaha: This is being fun fsom a script.. it can't join ehe sessiin
<kixkland> nkemeier: rigrt, so you freatc the session detacjed
<nigmeyer> kirkland: Jou don't have to reproduce the cece.. any solutoot wpll do :-)
<kixkland> niemeyer: somq people creatg their bvobu sdssion in z cronjmb at boot
<kyrkland> niemefgr: so that thxy can latnch irswi and jre byobu+irssi ss their
kirkland: If the same user executes the twice different terminals, command should fail never two different sessions kirkland: We can't the session, though.. <niemeyer> kirkland: Simply + exec command in new session, without races <kirkland> niemeyer: to reproduce the you're experience in screen... <kirkland> niemeyer: i'm going to create a screen session "screen debug" niemeyer: now I have a session <kirkland> niemeyer: called 'debug' <kirkland> niemeyer: and now I want to a command in that sesion <niemeyer> Ok <niemeyer> You want to create if it doesn't exist, and it the single <kirkland> okay, the "at" command niemeyer: i mean, screen's at <niemeyer> kirkland: Executing the command isn't the problem.. the problem is creating session in way <kirkland> byobu %s-hook-debug shell <kirkland> niemeyer: you were using before, right? <kirkland> what you found to be racy? <niemeyer> kirkland: that'd join session <kirkland> niemeyer: what were you to create it? <kirkland> niemeyer: i'm trying to the race <niemeyer> kirkland: This is being run from a script.. it can't join the niemeyer: right, so you the session detached kirkland: don't to the race.. solution will do :-) <kirkland> niemeyer: some people create their byobu in a cronjob at boot <kirkland> niemeyer: so that they irssi use byobu+irssi as
 kirkland: If the same user execUtes the samE commAnd TwiCe In diFferEnt terminals, thE CommAnd should fail or succeed, But it ShOUld nEVeR yielD two difFErENT seSsIoNs
<nIeMEyEr> kirKlaNd: We can'T _join_ the seSsiOn, Though..
<niemeyER> kIrkland: SimPly New-session + exEc cOmmand In New SEssioN, wiThout Races
<kIRkland> Niemeyer: tO rEProducE The probLEM yOu're Experience in screeN...
<KiRKland> niemeyer: i'M going To CReATE a sCreEn session wItH "screEN -S debug"
<KIrKLANd> nIEmeyer: okay, now i have a sessiON
<kiRkland> NiEmeYEr: callEd 'debUg'
<KIrkLand> niemeyeR: and Now I want tO run a cOMmand in THat sesiOn
<niemEyeR> Ok
<NiemEYeR> kIrkLaND: YoU WaNt tO CreAte it if iT dOeSn't exIst, aND RUN it iN thE sinGle seSsion
<kirkland> NieMeyeR: OkaY, usinG the "aT" comMaNd
<kirKland> nIemeyEr: I mean, screen's at
<nIemeYer> kirklaNd: EXeCutInG the cOMmand iSn't The Problem.. The probLEm iS cREATiNg the session in a non-RaCY WaY
<kirklanD> niemeYEr: ByOBu -xRS %s-hoOk-DebUg -t sHELl
<kirKlanD> NiEmeyer: thAt's whaT YoU wEre usinG bEfore, rIgHt?
<kIrkLand> nIEmeyEr: and tHat's what You foUNd to be racy?
<niemEYer> kirkland: No, THaT'D JoIN the SesSion
<kirklanD> nieMEyer: What WErE yoU Using To creAtE It?
<KIrkland> niemeyer: i'm trYiNg to reProduCe the race
<niemEyer> kirklaND: tHis is beiNg ruN FrOM a script.. it can't Join tHe session
<kIRkland> niEmeyeR: right, so You create THE session DetAchEd
<nIemEYEr> Kirkland: You doN'T Have To ReproduCe tHe race.. aNy sOluTioN wiLl Do :-)
<kirklanD> niemeyeR: sOmE pEoPle CreatE Their byoBu SesSiOn iN a croNJob at bOot
<kiRklaNd> NiEMeyEr: so thaT ThEY Can lAuNcH irsSi aNd Use byObu+iRSsi As their
 kirkland: If the same use r executes  thesam e c om mand  twi ce in differen t  ter minals, the command sh ouldfa i l or su cceed , but i t  s h o uld  n ev eryi e ld  twodif ferentsessions
< nie me yer> kirklan d :We can't _ joi n_ the sessi on,  thoug h. .
< n iemey er>  kirk land:S implynew-sessi on + exec command i nnewsession, withoutr ac e s
<kirkland> n iemeye r: to r epr odu ce the pro bl em yo u 're exp e ri e n c e i n  screen...
<k irkland> ni e mey er: i' mgoi n g to c reate  a scr een session  wit h "screen  -S de b ug"
<ki r kland>niemey er:  ok ay,n ow  I  ha ve a s e ss ion <ki rkland>ni em eyer:  cal l e d 'deb ug' 
<ki rklan d> niemeyer:and  now I w ant t o run  a c om mandin tha t ses io n
<niemeyer> Ok 
<ni emeyer> k irk la nd:  Y ou wa n t to c rea teit if i t doesn ' t e xi s t ,  a nd run it in the s in g l esession<kirkl a nd >n iemeyer:  o kay , us i n g the  "at "  c ommand
< kirkla n d>  n iemeyer :i mean ,scr een 's at <nie meyer>  kirklan d: Ex e cuting the com m and isn't the pr o b le m .. t heproblem iscrea t ingthes es sio n  in a  non- ra c yw ay
<kirkland> nieme ye r: byo bu -x RS %s-hook-de bug -t she l l <kirklan d> n i em e yer: that's wh at yo u were usi n g before , rig ht?
<kir kland> ni e m eyer: an d t hat 'swha t yo u found to be r acy? 
< niemeye r>kirklan d:No,  th at' djoin thesession<k ir kl an d>nieme y er: what  w ere  y ouusing to cre ate i t?
< ki rk l and > nieme y er : i'mtr yi ng t o r ep roduc e th e  ra ce
<nie meyer> ki rkl a nd:Th is  is bei ng run from a  s cript.. it  c an' t join t he sessi on
<kirkland> niemeyer: right,soyou c reat e the ses sio n deta che d 
<niem eyer>kirkl an d:Y o u don ' t  h ave  t o reproduc e the  race ..  any  soluti on will do :-)
<ki r kla nd> niemeyer:  so me p e o pl e c r ea t e t he i r b y o bu session in a  cronjob a tb oo t
<kirklan d > n ie meyer:so that  they can lau nch irssi  and useby obu+ i r ssi  as their
 kirkland:_If the_same user executes the_same command_twice_in different_terminals,_the command should_fail or succeed,_but it should never_yield two different_sessions
<niemeyer>_kirkland: We can't _join_ the session, though..
<niemeyer> kirkland: Simply new-session + exec command in_new_session, without_races
<kirkland>_niemeyer:_to reproduce the problem you're_experience in screen...
<kirkland> niemeyer: i'm_going to_create a screen session with "screen -S debug"
<kirkland>_niemeyer:_okay, now I_have a session
<kirkland> niemeyer: called 'debug'
<kirkland> niemeyer: and now_I want to run a command_in that sesion
<niemeyer>_Ok
<niemeyer>_kirkland:_You want to create_it if it doesn't exist, and_run it in the single session
<kirkland>_niemeyer: okay, using the "at" command
<kirkland> niemeyer:_i mean, screen's at
<niemeyer> kirkland: Executing_the command isn't the problem.._the problem_is creating the session in_a non-racy way
<kirkland>_niemeyer: byobu_-xRS %s-hook-debug -t_shell
<kirkland> niemeyer: that's what you were_using before, right?
<kirkland>_niemeyer: and that's what you found_to_be racy?
<niemeyer> kirkland:_No,_that'd_join the_session
<kirkland> niemeyer: what_were_you using_to_create it?
<kirkland> niemeyer: i'm trying to_reproduce_the race
<niemeyer> kirkland: This is being run_from a script.. it_can't_join the session
<kirkland> niemeyer:_right, so you create the_session detached
<niemeyer> kirkland: You don't have_to reproduce_the race.._any solution will do :-)
<kirkland> niemeyer: some people create their byobu_session in a cronjob at boot
<kirkland>_niemeyer: so that they_can launch_irssi_and use byobu+irssi_as_their