[Contents] [Prev] [Next] [Index] [Report an Error]

Assigning a Transfer Delay to an Event Policy Action

A transfer delay allows you to specify the number of seconds the event process (eventd) waits before beginning to upload a file or multiple files. A transfer delay allows you to ensure that a large file, such as a core file, is completely generated before the upload begins.

As described in Defining Destinations for File Archiving, you can associate a transfer delay with a destination. If you associate a transfer delay with a destination, the transfer delay applies to all file upload actions that use the destination.

In the following example, the some-dest destination is common for both event policies, policy1 and policy2. A transfer delay of 2 seconds is associated with the some-dest destination and applies to uploading the output files to the destination for both event policies.



[edit event-options]
policy policy1 {
events e1;


then {




execute-commands {


commands {
"show version";
}


output-filename command-output.txt;
destination some-dest;
}


}
policy policy2 {
events e2;


then {


event-script bar.xsl {
output-filename event-script-output.txt;
destination some-dest;
}


}


}
destinations {


some-dest {
transfer-delay 2;


archive-sites {
"http://robot@my.big.com/foo/moo" password "password";
"http://robot@my.little.com/foo/moo" password "password";
}


}


}

Suppose you have multiple event policy actions that use the same destination. For some of these event policy actions, you want a transfer delay, and for other event policy actions you want no transfer delay. To assign a transfer delay to a single event policy action, include the optional transfer-delay statement for each action:




transfer-delay seconds;

You can include this statement at the following hierarchy levels:

[edit event-options policy policy-name then event-script script-name destination destination-name]
[edit event-options policy policy-name then execute-commands destination destination-name]
[edit event-options policy policy-name then upload filename filename destination destination-name]

If you configure a transfer delay in the destination definition (at the [edit event-options destinations destination-name] hierarchy level), and you also configure a transfer delay for the event policy action, the resulting transfer delay is the sum of the two:



Total transfer-delay = 
transfer-delay (destination) + transfer-delay (event-policy-action)

For configuration examples, see Assigning a Transfer Delay to an Event Policy Action.

[Contents] [Prev] [Next] [Index] [Report an Error]