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)
I am using Expect to spawn a command that loops through a text file and runs the same command for each item in the text file.
The text file, named stat.txt looks something like this:
2007-04 alist 543
2008-07 blist 543
2008-03 xlist 345
2008-03 ylist 675
2003-03 zlist 567
The expect... (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)
I must automatically monitor and manage a large number of boxes on our network.
I have been using perl/Net::Telnet and expect/telnet and also perl/ssh and expect/ssh to reach the command line of the remote boxes. Scripts are working but slow.
(Yes, I do use SNMP also but many boxes do not... (2 Replies)
Hi All,
I am trying to write a expect script to telnet and run a command on a remote host.The command i want to send contains a text value is contained in file.txt in the linux box from where i am running the expect script.I want to pass the contains of file.txt into a variable and call the... (1 Reply)
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)
I've got some expect/tcl scripts.
Now i want to add a function that allows to open a telnet connection and redirect the output to a logfile.
On the shell/terminal i tried something like:
'telnet 192.168.123.123 12121 > /home/user/logging/log-telnet.log'
and the telnet is redirected into the... (2 Replies)
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)
Hi All,
I have an Expect script which logs into Cisco switch, performs a show interface command. I want to read a file of ip addresses which will be passed to the expect script.
The script to read the file works, the expect script works on it's own but when i call the 'expect' script from the... (12 Replies)
hi, please help, keep getting this bolded error and look it up and people say
its your environment variable though i tried to set it manually in expect..it run fine if i run it manually but once i run it by cronjob it error below..i tried to comment out ip/login info with *..
logfile::
START... (0 Replies)
Discussion started by: cssanangeles
0 Replies
LEARN ABOUT NETBSD
env
ENV(1) BSD General Commands Manual ENV(1)NAME
env -- set and print environment
SYNOPSIS
env [-i] [name=value ...] [utility [argument ...]]
DESCRIPTION
env executes utility after modifying the environment as specified on the command line. The option name=value specifies an environmental
variable, name, with a value of value. The option '-i' causes env to completely ignore the environment it inherits.
If no utility is specified, env prints out the names and values of the variables in the environment, with one name=value pair per line.
EXIT STATUS
env exits with one of the following values:
0 utility was invoked and completed successfully. In this case the exit code is returned by the utility itself, not env. If no util-
ity was specified, then env completed successfully and returned the exit code itself.
1 An invalid command line option was passed to env.
1-125 utility was invoked, but failed in some way; see its manual page for more information. In this case the exit code is returned by the
utility itself, not env.
126 utility was found, but could not be invoked.
127 utility could not be found.
COMPATIBILITY
The historic - option has been deprecated but is still supported in this implementation.
SEE ALSO execvp(3), environ(7)STANDARDS
The env utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
BUGS
env doesn't handle commands with equal (``='') signs in their names, for obvious reasons.
BSD June 8, 2007 BSD