9 More Discussions You Might Find Interesting
1. Programming
I'm fairly new to scripting so this might not be possible.
I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version:
#show version
... (0 Replies)
Discussion started by: IBGaryA
0 Replies
2. Shell Programming and Scripting
Hi I have the following Korn script having multiple for loops.
#!/bin/ksh
EXPECT=/usr/local/bin/expect
exp_internal
for d in 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 i22 23 24 25 26; do
for i in 01 02 03 04 05 06 07 ; do
for h in 00 01 02 03 04 05 06 07 08 09 10 11 12... (2 Replies)
Discussion started by: cic
2 Replies
3. Shell Programming and Scripting
Hi,
I am trying to incorporate multiple while loops into an expect script written in ksh shell. This is on a Solaris 10 system. Here is the code:
#!/bin/ksh
EXPECT=/usr/local/bin/expect
exp_internal
i=1
h=0
while ]; do
$EXPECT << DONE
set stty_init raw
... (1 Reply)
Discussion started by: cic
1 Replies
4. Shell Programming and Scripting
Hi
First of all I tried lot of forums to create my first expect script. But I am totally stumped at the last step. I am no Linux Admin or ever trained in Linux. I just tried to create the script logically
History :
I need to to change my password across lot of servers in Linux over ssh
... (4 Replies)
Discussion started by: radioactive9
4 Replies
5. Shell Programming and Scripting
Dear experts, please help me .
I've found simple EXPECT scripts and all works fine. But I need more automation in error handling and sending list of commands/output logging from multiple remote hosts.
I have 10 hosts, for example:
host1 192.168.1.1 LOGIN1 PASSWORD1
...... ... (2 Replies)
Discussion started by: starchen
2 Replies
6. Shell Programming and Scripting
Hello, this is probably a simple request but I've been toying with it for a while.
I have a large list of devices and commands that were run with a script, now I have lines such as:
a-router-hostname-C#show ver
I want to print everything up to (and excluding) the # and everything after it... (3 Replies)
Discussion started by: ippy98
3 Replies
7. Shell Programming and Scripting
Hello All,
I am trying to automate an installation process using expect and sh script. My problem is that during the installation process the expected value can change according to the situation.
For Example if this is a first time installation then at step 3 I'll get "Do you want to accept... (0 Replies)
Discussion started by: alokrm
0 Replies
8. Shell Programming and Scripting
This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies
9. Shell Programming and Scripting
Hello to all...this is my first post (so please go easy). :)
I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies
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)