There *has* to be an elegant way to do this in Expect...
I have a command that returns lines of numbers. Like:
prompt% mycommand --loop=5
9 4956 4951 4951 4956
9 4960 4951 4951 4956
9 4956 4951 4951 4956
9 4956 4951 4951 4956
9 4956 4951 4951 4956
prompt%
All numbers must be... (0 Replies)
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)
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)
Hi I have a working expect script below. The script continues to log cisco router configurations until all the ip addresses in the "routerlist1" has been read. Problem will start to happen when one of the ip address is not reacheable via ssh or telnet. The script will stop to read the rest of the... (2 Replies)
Hi,
I am trying to write an expect script. Being a newbie in expect, maybee this is a silly doubt but i am stuck here.
So essentially , i want the o/p of one router command to be captured . Its something like this
Stats
Input Rx : 1234
Input Bytes : 3456
My expect script looks ... (5 Replies)
Hello,
I tried to use expect to catch information from my nagios and send me a call but i have nothing when i execute the script :
0 - add : account SIP
1 - trext : information from nagios
text2wav : conversion text to wav ( text to speech )
pjsua : connection thru the SIP
... (0 Replies)
I was wondering if I could do this a bit better.
another script calls this script and logs into a device, does the relavant "show commands" and then saves those to a file.
My problem is that the buffer isn't large enough to the output of some of the commands.
here is an excerpt of what i'm... (0 Replies)
Hi
I am new to IP configuration and using expect script
I have a requirement like
I need to write a expect script that can ssh to a remote machine(linux1) using password which already has IP, once logged inside machine need to reboot remote machine(linux1) and again login to same remote... (1 Reply)
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
LEARN ABOUT DEBIAN
exim_convert4r4
EXIM_CONVERT4R4(8) System Manager's Manual EXIM_CONVERT4R4(8)NAME
exim_convert4r4 - Convert Exim configuration from v3 to v4 format
SYNOPSIS
exim_convert4r4
DESCRIPTION
This script is provided to assist in updating Exim configuration files. It reads an Exim 3 configuration file on the standard input, and
writes a modified file on the standard output. It also writes comments about what it has done to the standard error file. It assumes that
the input is a valid Exim 3 configuration file. A typical call to the conversion script might be
exim_convert4r4 < /etc/exim/exim.conf > /etc/exim4/exim4.conf.new
The output file MUST be checked and tested before trying to use it on a live system. The conversion script is just an aid which does a lot
of the "grunt work". It does not guarantee to produce an Exim 4 configuration that behaves exactly the same as the Exim 3 configuration it
reads.
Each option change in the new file is preceded by an identifying comment. In fact, the conversion script tends to make quite a mess of
your configuration, and you should expect to go through it afterwards and tidy it up by hand.
Unless you are running a very straightforward configuration, the automatic conversion is likely to generate a non-optimal configuration.
You should not only check it thoroughly, but also run as many tests as you can, to ensure that it is working as you expect. In particular,
you should test address routing, using -bt and -bv, and the policy controls, using -bh. If possible, you should also do some live tests
(i.e. send and receive some messages) before putting Exim 4 into service.
If you have a very complicated configuration, it is possible that exim_convert4r4 will break it in some situations, which is why thorough
testing is strongly recommended.
BUGS
This manual page needs a major re-work. If somebody knows better groff than us and has more experience in writing manual pages, any patches
would be greatly appreciated.
SEE ALSO exim(8), the files in /usr/share/doc/exim4-base/, especially Exim4.upgrade.gz
AUTHOR
This manual page was stitched together from Exim4.upgrade by Andreas Metzler <ametzler at downhill.at.eu.org>, for the Debian GNU/Linux
system (but may be used by others).
March 26, 2003 EXIM_CONVERT4R4(8)