Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
connection timedout

Posted by priyadharshini (priyadharshini), 9 May 2008
hi,

        I've a problem with remote access. I'm telnetting to a pc(let it be 134) through putty. From 134 I'm telnetting to a linux pc(143). In 143 machine i stored all of my tcl files since my pc and 134 are not having tcl installation. from 143 machine 'm running my scripts. The script needs 6 hrs to run completely. there should not be any manual intervention while the script is running. The script will make telnet connection with different routers, send commands to them and then captures their output buffer. Since the console is idle for a long period the telnet connection gets lost and the execution of scripts stops in the middle. Can any one help to fix this issue?
       I guess the telnet connections established by the scripts don't 've any problem. either the telnet from my pc to 134 or telnet from 134 to 143 is getting lost.

Thank you,

Posted by admin (Graham Ellis), 9 May 2008
How about backgrounding the scripts on 143 (an & on the end of the command line) and redirecting the output to a file.  When you disconnect / timeout the process will continue, and you can monitor it non-intrusively via a tail.  Have a look at at and batch commands on Linux too.

Posted by priyadharshini (priyadharshini), 12 May 2008
hi,

 I changed the seconds between keepalives. Now the sesion s not getting timed out before the completion of script execution.

Thank ypu,



This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho