I am in a situation where I need to connect to a list of devices that are using either telnet or ssh.
I want to try to telnet, if I receive any of the following I want to attempt ssh :
hai all,
i have an tcl script in which i have been reading the DUT Command prompt of an cisco switch as
DUT Command Prompt : cisco*
and running the test case of stp now the problem is if i have given any blank space in between the cisco or at the startup then the Expect is not identifying the... (0 Replies)
Does anyone know of an expect/tcl forum that is as helpful as this one is for shell scripting?
Or if anyone has any expect knowledge, can you please provide some guidance on how to write to a local error log based on output from a ssh session?
I have something like this:
foreach host... (2 Replies)
In the following "for" loop I assume the the script will expect "anyway", "first" NOT in any paticular order and send "yes" when there found, breaking out of the loop when "$prompt" is found. The way it is working is like 3 individual expect lines, and they MUST be in cronological order. ANY help... (0 Replies)
Can someone identify what is the problem here?.
no children
while executing
"exp_wait -nowait -i -1"
(procedure "logOptions" line 45)
invoked from within
"logOptions"
(procedure "doExecute" line 98)
invoked from within
"doExecute"
(procedure "main" line 32)
... (7 Replies)
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
So here is what I am trying to do. I have a large # of switches and routers I am trying to log into. Unfortunately some have ssh only, some have telnet only. and some i have never logged into with ssh. I first want it to SSH, if i have never logged into the box it will ask for adding the ssh key. I... (0 Replies)
hi, I am new in Expect.
I have a question about expect timeout.
suppose I have a structure of
expect { ".."{
send"............"}
timeout{
...............
}
}
The silly question is if I reach timeout, how can I store the error message showing on the screen to... (2 Replies)
Hi gurus, I am trying to do some expect/TCL magic. My goal is to write some kind of password guessing script (nearly similar to dictionary attack against ssh). I read that this could be possible with expect/TCL, I am newbie in this language, its function and its terms so please be patient ;)
... (3 Replies)
The below error message I started seeing using Ubuntu 14.04 and was wondering if the forum has seen it because I cant seem much on the net for this:
perl -e 'use IO::Socket::SSL qw(debug3);IO::Socket::SSL->new(PeerAddr=>"10.0.0.100",PeerPort=> 443,Proto=>"TCP") or die $!'
DEBUG:... (1 Reply)
Discussion started by: metallica1973
1 Replies
10. Forum Support Area for Unregistered Users & Account Problems
Neo
Thanks for your reply to my original post, entitled "Problem changing the email address associated with my unix.com account".
I am unable to reply to you in that thread, as I am unable to log-on to unix.com!
From what you said about purging dormant accounts, it is likely that my account... (1 Reply)
Discussion started by: irb
1 Replies
LEARN ABOUT DEBIAN
parallel-ssh
pssh(1) General Commands Manual pssh(1)NAME
pssh -- parallel ssh program
SYNOPSIS
pssh [-vAiIP] [-h hosts_file] [-H [user@]host[:port]] [-l user] [-p par] [-o outdir] [-e errdir] [-t timeout] [-O options] [-x args] [-X
arg] command ...
pssh -I [-vAiIP] [-h hosts_file] [-H [user@]host[:port]] [-l user] [-p par] [-o outdir] [-e errdir] [-t timeout] [-O options] [-x args] [-X
arg] [command ...]
DESCRIPTION
pssh is a program for executing ssh in parallel on a number of hosts. It provides features such as sending input to all of the processes,
passing a password to ssh, saving output to files, and timing out.
OPTIONS -h host_file
--hosts host_file
Read hosts from the given host_file. Lines in the host file are of the form [user@]host[:port] and can include blank lines and com-
ments (lines beginning with "#"). If multiple host files are given (the -h option is used more than once), then pssh behaves as
though these files were concatenated together. If a host is specified specified multiple times, then pssh will connect the given
number of times.
-H [user@]host[:port]
--host [user@]host[:port]
-H "[user@]host[:port] [ [user@]host[:port ] ... ]"
--host "[user@]host[:port] [ [user@]host[:port ] ... ]"
Add the given host strings to the list of hosts. This option may be given multiple times, and may be used in conjunction with the
-h option.
-l user
--user user
Use the given username as the default for any host entries that don't specifically specify a user.
-p parallelism
--par parallelism
Use the given number as the maximum number of concurrent connections.
-t timeout
--timeout timeout
Make connections time out after the given number of seconds. With a value of 0, pssh will not timeout any connections.
-o outdir
--outdir outdir
Save standard output to files in the given directory. Filenames are of the form [user@]host[:port][.num] where the user and port
are only included for hosts that explicitly specify them. The number is a counter that is incremented each time for hosts that are
specified more than once.
-e errdir
--errdir errdir
Save standard error to files in the given directory. Filenames are of the same form as with the -o option.
-x args
--extra-args args
Passes a extra SSH command-line arguments (see the ssh(1) man page for more information about SSH arguments). This option may be
specified multiple times. The arguments are processed to split on whitespace, protect text within quotes, and escape with back-
slashes. To pass arguments without such processing, use the -X option instead.
-X arg
--extra-arg arg
Passes a single SSH command-line argument (see the ssh(1) man page for more information about SSH arguments). Unlike the -x option,
no processing is performed on the argument, including word splitting. To pass multiple command-line arguments, use the option once
for each argument.
-O options
--options options
SSH options in the format used in the SSH configuration file (see the ssh_config(5) man page for more information). This option may
be specified multiple times.
-A
--askpass
Prompt for a password and pass it to ssh. The password may be used for either to unlock a key or for password authentication. The
password is transferred in a fairly secure manner (e.g., it will not show up in argument lists). However, be aware that a root user
on your system could potentially intercept the password.
-i
--inline
Display standard output and standard error as each host completes.
-v
--verbose
Include error messages from ssh with the -i and options.
-I
--send-input
Read input and send to each ssh process. Since ssh allows a command script to be sent on standard input, the -I option may be used
in lieu of the command argument.
-P
--print
Display output as it arrives. This option is of limited usefulness because output from different hosts are interleaved.
EXAMPLE
Connect to host1 and host2, and print "hello, world" from each:
pssh -i -H "host1 host2" echo "hello, world"
Print "hello, world" from each host specified in the file hosts.txt:
pssh -i -h hosts.txt echo "hello, world"
Run a command as root with a prompt for the root password:
pssh -i -h hosts.txt -A -l root echo hi
Run a long command without timing out:
pssh -i -h hosts.txt -t 0 sleep 10000
If the file hosts.txt has a large number of entries, say 100, then the parallelism option may also be set to 100 to ensure that the com-
mands are run concurrently:
pssh -i -h hosts.txt -p 100 -t 0 sleep 10000
Run a command without checking or saving host keys:
pssh -i -H host1 -H host2 -x "-O StrictHostKeyChecking=no -O UserKnownHostsFile=/dev/null -O GlobalKnownHostsFile=/dev/null" echo hi
EXIT STATUS VALUES
0 Success
1 Miscellaneous error
2 Syntax or usage error
3 At least one process was killed by a signal or timed out.
4 All processes completed, but at least one ssh process reported an error (exit status 255).
5 There were no ssh errors, but at least one remote command had a non-zero exit status.
AUTHORS
Written by Brent N. Chun <bnc@theether.org> and Andrew McNabb <amcnabb@mcnabbs.org>.
http://code.google.com/p/parallel-ssh/
SEE ALSO ssh(1), pscp(1), prsync(1), pslurp(1), pnuke(1)
February 25, 2010 pssh(1)