Task properties

General options

Figure 6: Task properties

Properties	Information	Example
Use	Template identifier for this task. This template makes it possible to use default options.	identifiant
Id	Represent the identifier of the task. It is used in all the job to identify in a single way the task.	identifiant
Command	What you want to execute (command line)	tar cfvz /bkp.tgz /etc
Host	This fields makes it possible to specify on which server, the task will be execute.	serveur1
Comment	Comments	comment
Condition	Script of condition which is execute before command execution. This script must return a true value to authorized task execution (Cf 6.1).	ok('before-sleep')

Input/Output Options

Figure 7: I/O Task properties

Properties	Information	Example
stdin	The input stream is referred to as ``standard input''	/etc/passwd
stdout	The output stream is referred to as ``standard output'' (default set to ${ID}.stdout) Warning, file outside of work_dir are not initialized with right permissions (user/group).	file.out
stderr	The error stream is referred to as ``standard error''. (default set to ${ID}.stderr) Warning, file outside of work_dir are not initialized with right permissions (user/group).	file.err

Visualization with sched_view

To visualize log file with sched_view, files must be in work_dir (current directory).

Other options

Figure 8: Task properties (other options)

Properties	Information	Example
After Exec	Script executed after the execution of the command. This script can be used to send mail or alarm for example. (see 6.1 )	ok('sleep') or job_end(1)
Max exec time	Maximum time of execution of a task (in second). At the end of this time the task finishes in error (exit code 127) (kill by signal 15 then signal 9).	60
User	This is used to set the effective user that the command process should run as. You may specify either a username or a UID. Warning, standard personal initialization files are not read.	root
Group	This is used to set the effective group that the command process should run as. You may specify either a groupname or a GID.	root
Env	Variable of environment. Variables placed here will be exported before task execution.	HOME=/root

Variables

Use case

Variables are valid in these following entry :

• command line (cmdline)
• standard error (stderr)
• standard output (stdout)
• standard input (stdin)
• effective user (user)
• effective group (group)
• target host (host)
• condition script (cond)
• after execution script (after_cmd)

Format

Variables have the format :

[a-zA-Z0-9-_]+

Substitution

The variable is used like as in Shell. (${VAR}). The variables are not added in the program execution environment.

The variables are substituted at the task loading. (first execution attempt).

It is possible to use the strftime(3) format in the string. But the execution of an order can be delayed, so do not use precise time-stamping.

System defined variables

ID

: id of current task

SERIAL

: unique id of current job

HOSTNAME

: name of local host

Example

Variable :

DATE = date-%Y%M%D

On command for example (cmdline) :

tar tfz backup_${DATE}.tgz => tar tfz backup_date-20050210.tgz

Environment variables

It is possible to use variables of environment on the level of the job (valid for all tasks) and on the level of each task (field env). These variables are usable even if the task is executed on another host.

Format

You must have one variable by line, and no empty line.

    VAR1=/home
    VAR2="/home"
    VAR3=/home /home2 home4
    VAR5='/home1 /home2'

Restriction

You can't use substitution. For example :

    VAR1=mavariable
    VAR2=${VAR1}2

These don't work.