Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Our network involves a series of dumb text terminals which telnet into a SCO OpenServer 6 server. Occasionally, one of these terminals will crash, forcing the operator to move to a different terminal until the broken terminal is either repaired or replaced.

This normally leaves hanging processes, and the related annoyances of important files not being closed down properly. Rather than manually killing the processes and closing/repairing the unclosed files, it would be so much more practical to just 'reattach' the existing processes to the new terminal and allow the operator to continue as if nothing happened.

So the question is: Is this even possible? And if so, what is the best way for me to go about doing it?

share|improve this question

3 Answers 3

up vote 14 down vote accepted

This is what the 'screen' utility was invented for. Although I've used it mainly on Linux, there's absolutely no reason a port for your OS couldn't exist. It's part of the gnu tool set, and I haven't found a port, but one probably exists (or could).

share|improve this answer
    
+1 spot on. Screen is invaluable for unreliable network connections or long running processes. –  David Pashley Jun 6 '09 at 19:14
    
I have screen on OS X through macports. Was typing this same answer too and noticed yours ;) –  l0c0b0x Jun 6 '09 at 19:19
    
screen looks like it will do exactly what I need. My only concern is that the existing system is not at all set up to handle VT100. –  goldPseudo Jun 7 '09 at 0:31
1  
Yep, does exactly what I was looking for. For reference, SCO OSR6 port of screen is available at sco.com/skunkware. –  goldPseudo Jun 8 '09 at 23:50

Screen is wonderful, as the previous answer has noted. It will probably solve your issue. For situations where screen is not appropriate (i.e. running a background task) look at nohup.

share|improve this answer

As the other two responders have noted screen is specifically intended for this use, and has a number of other useful features too.

I have set a number of hosts I connect to to run screen on each login, so I don't forget and only notice when something happens to cause an unexpected disconnect by which point it is too late. See http://tlug.dnho.net/?q=node/239 for one example of setting this up.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.