16-User Network

[Fairlight]

At Tue, Aug 30, 2011 at 11:21:38PM -0400 or thereabouts, 
suspect Brian K. White was observed uttering:
> Start a job in the office, disconnect from it, go home, reconnect to it.
> 
> Start a job that absolutely must not be interrupted, in screen, and it's 
> OK if your net connection farts, your pc crashes, etc. No problem, the 
> app never gets a hangup. Nohup or trap are not always as desirable as 
> simply having a disconnectable/reconnectable session. Note I keep saying 
> disconnect/reconnect, not suspend/resume or even background/foreground.

There's a network engineer that refuses to fix the bloody SonicWall idle
timeout on -one- server.  Drives me around the bend with this 10min idle
disconnect, when I'm not -technically- idle, the process I'm waiting on
just isn't outputting anything.  

Every time I have to do something with this server like a big OS-wide
task or a big file transfer, or some other process that doesn't output to
STDOUT, and which can't be backgrounded (there is at least one), I throw
screen up and work from in there so that I can let it finish and just
reconnect to see the results or continue the task.  I've all but given hope
of him fixing the damned firewall, so I've got my own workaround.

Autodetach is godlike.  Always has been since I used it back in '90-91.  (I
started with window(1) on BSD 4.3 in '89, but moved to screen(1) when we
moved to Ultrix.)  Wish I could remember how to use screen splitting in
screen, though.  Been years.  I tinkered with it a little a month ago but
didn't get to the point I remembered how to use it correctly.  Used to
know...  That was more window's strength...splitting the screen both
horizontally and vertically, as much as you needed.

mark->
-- 
Audio panton, cogito singularis.