Hello all,
It's been a few years since I touched 'expect' and just got it on my system.
In the past, I could simply do the following:
(this is just a simple example)
$ expect
$ ls -l
$ pwd
$ exit
...then a default script name would be placed in my working directory. At this point I... (2 Replies)
I need to run a remote application(GUI) in a client.i.e on running a script in the client machine i should get the GUI application which is running in the server by providing password through the script.Will expect or autoexpect command suit for this scenario?
could anyone help me by posting some... (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)
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)
Hi,
Am very new to expect scripting..
Can You please suggest me how to call an expect script inside another expect script..
I tried with
spawn /usr/bin/ksh
send "expect main.exp\r"
expect $root_prompt
and
spawn /usr/bin/ksh
send "main.exp\r"
expect $root_prompt
Both... (1 Reply)
I have a simple Expect script to power a system on and off in an endless loop looking for an ERROR message at which point the script should exit. But I need to skip the first 60 seconds after each power on or off and not exit if there are ERROR messages during that time. I thought I could use... (0 Replies)
the following code works sometimes. other times, it behaves mysteriously. when the script sshs to a box, it is suppose to automatically begin running the command it is told to run. but in this case, after this script logs into a host, it just sits there at the prompt and does not run the... (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
rdeliver
rdeliver(1) General Commands Manual rdeliver(1)NAME
rdeliver - Ruby mail filter script
SYNOPSYS
rdeliver <options> [script]
DESCRIPTION
This script serves as an example of how you can use the RFilter::DeliveryAgent class to perform mail delivery. You can also use this
script as a fully functioning mail filter.
This script is a basic mail local delivery agent (DeliveryAgent) that can be used in place of procmail, maildrop, etc. in a user's .forward
or .qmail file. The user supplies a delivery script that is written in Ruby, which avoids the limitations of the crippled mini-languages
so often used in other DeliveryAgent programs.
USAGE
rdeliver is invoked from the command line using:
% rdeliver <options> [script]
The script argument is optional. If omitted the script will look for a file called .rdeliver in the home directory.
Options are:
--load-path directory
Prepend the given directory to ruby's load path.
--log filename
Log to the given filename. If no log is specified, no logging occurs.
--home directory
Specify the home directory. rdeliver will change to this directory before reading and writing any files. The home directory
defaults to the value of the HOME or LOGDIR environment variable.
DELIVERY SCRIPT
The delivery script runs in the context of a class called Deliver (in contrast, most ruby scripts run in the context of the Object class).
So any methods added with def will be added to the Deliver class.
A minimal delivery script would be:
def main
agent.save('inbox')
end
This code defines a Deliver#main method that saves the mail into an mbox style mailbox.
The only API the Deliver script has is the #agent method. This retrieves the RFilter::DeliveryAgent object associated with the current
message. Using the API of the RFilter::DeliveryAgent object, you can access and modify the message body and headers, defer or reject the
message delivery, and deliver into various mailbox formats.
See also RFilter::DeliveryAgent and Deliver.
INSTALLATION
Assuming you have the RubyMail mail classes installed, you typically have to put something like this in your .forward file:
|"/usr/bin/rdeliver --log /home/you/.rlog"
This will call rdeliver for each new message you get, and log to /home/you/.rlog.
CATASTROPHIC ERRORS
The rdeliver script is very careful with errors. If there is any problem, it logs the error to the log file you specify. But if you do
not specify a log file, or the error occurs before the log file is opened, a record of the error is placed in a file called CATASTROPH-
IC_DELIVERY_FAILURE in the home directory. If that fails, the error information is printed to the standard output in the hopes that it
will be part of a bounce message. In all cases, the exit code 75 is returned, which tells the MTA to re-try the delivery again.
AUTHOR
rdeliver and RFilter support classes were written by Matt Armstrong <matt@lickey.com>.
This document was originally an RD format document of rdeliver script. This manual page was converted from it for Debian GNU/Linux system.
September 2003 rdeliver(1)