screen program information

[BURNS,JIM]

in article <13840 at hydra.gatech.EDU>, I write:

> Well, of course I could always just ^a-k (kill) that screen window w/o
> affecting any of my other windows, then ^a-c ((re-) create)
 that window if
> I need it.

Then again, I suppose this wouldn't be appropriate if the program needs to
update files after the output is finished, or then returns to interactive
communication, and you don't want to spend a lot of time reconstructing
the state of the program up to then. Does redirecting output of 'sess'
drain the output fairly quickly, or do you have to guess how long it
takes? Some netstat(1) output can take forever just to be generated!
-- 
BURNS,JIM
Georgia Institute of Technology, Box 30178, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt0178a
Internet: gt0178a at prism.gatech.edu