01-03-2018
How to break out of hung or waiting telnet session in shell script?
I have to put together telnet instructions for 100s of hosts for verifying basic connectivity and get output in a neat format.
Problem- If a telnet is hung with message "Trying .... <hostname" due to firewall or routing issue the commands waits for a very long time before it times out and my shell script gets to execute next command. Please advise how to breakout of such hung telnet and resume on next line.
Last edited by Scott; 01-03-2018 at 06:31 AM..
Reason: Removed Poll
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
{
sleep 2
echo "$user"
sleep 2
echo "$password"
sleep 2
echo " ls"
sleep 10
echo "exit"
}| telnet $server
I have a machine x and i have executed the above script on machine 'x'.
i entered the... (6 Replies)
Discussion started by: pathanjalireddy
6 Replies
2. UNIX for Dummies Questions & Answers
Hi
Is there any way whilst in a telnet session you can view your client machine name that you are using to connect to the Unix box ? :eek: (2 Replies)
Discussion started by: mlucas
2 Replies
3. Shell Programming and Scripting
I am using a shell script to telnet into a remote unix server and execute certain commands. But if any command being executed remotely, throws an error, the script just hangs. And the telnet session does not get closed.
I want to be able to close the session and complete the script execution in... (1 Reply)
Discussion started by: farahzaiba
1 Replies
4. HP-UX
Hi All,
Our server OS info:
HPUX-UNIX>uname -a
HP-UX hps B.11.11 U 9000/800 2983362429 unlimited-user license
We access our server from Windows m/c through telnet sessions. But for unknown reason any telnet sessions are getting hung after about 15 minutes idle time. Then we close it and... (2 Replies)
Discussion started by: mhbd
2 Replies
5. HP-UX
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies
6. Shell Programming and Scripting
Dear All,
The sqlplus 'Accept' command is not waiting for user input when I include the command within a shell script.
Note: The 'Accept' command is working fine if I execute it in a SQLPLUS Prompt.
Please fins the below sample script which i tried.
SCRIPT:
--------
#!... (4 Replies)
Discussion started by: little_wonder
4 Replies
7. Shell Programming and Scripting
Hi all,
I am currently running a daemon which creates a virtual terminal for testing purposes. Essentially, if I were to interact with it manually, this is what I get.
john@test1:~$telnet localhost 7777
Trying ::1...
Connected to localhost.
Escape character is '^]'
mip6d> pl
eth2... (6 Replies)
Discussion started by: abxccd
6 Replies
8. Shell Programming and Scripting
Hello people, I am creating a script that will alert me in an ftp or telnet account on my system expires. FTP part is ok, but when I am entering the 3 script, it stucks. I can see that the script will not close the telnet seession. Can you please check and let me know what I am doing wrong? What if... (7 Replies)
Discussion started by: drbiloukos
7 Replies
9. Shell Programming and Scripting
Hi,
I need to initiate a process script which will start and do some processing and then shuts down. Then i need to other verifications. But the the process takes around 25 to 3o minutes.
One thing i can monitor the nohup.out file for this process where i can wait for shutting down statement to... (3 Replies)
Discussion started by: Prashanth19
3 Replies
LEARN ABOUT OSF1
telnetrc
telnetrc(4) Kernel Interfaces Manual telnetrc(4)
NAME
telnetrc, .telnetrc - Specifies setup commands for a telnet session
SYNOPSIS
$HOME/.telnetrc
DESCRIPTION
The .telnetrc file contains the setup information for a telnet session. It is a hidden file in your home directory and must be readable by
the user logging in.
The file can consist of multiple entries for each remote host to which a user can connect. A remote host entry consists of multiple lines.
The first line is the name of a remote host. The subsequent lines must begin with blank spaces, and contain telnet subcommands. These sub-
commands are processed as though they were typed in manually. Lines beginning with a number sign (#) are comment lines. See telnet(1) for
a complete list of telnet subcommands.
To specify subcommands that apply to all systems, create an entry, using the word "DEFAULT" as the system name, and specify the telnet sub-
commands in the subsequent lines.
EXAMPLES
The following shows a sample .telnetrc file:
# Beginning of telnetrc file # Default subcommands that apply to all systems DEFAULT
environ undefine USER # First system entry system1
set echo
toggle crlf # Second system entry system2
set echo
mode line
toggle crlf
FILES
User-customized telnet startup values.
RELATED INFORMATION
Commands: telnet(1). delim off
telnetrc(4)