System information

Using scripts in Axis Camera/Video products
Axis Communications AB provides NO support for application development of any kind. The information
here is provided "as is", and there is no guarantee that any of the examples shown will work in your
particular application.
Revision 1.02 October 2002 9
3.2.1 Syntax for /etc/task.list
An entry in /etc/task.list has the following syntax:
<event>%<program>:<args>;
<event> = is the event description
<program> = is the program to start
<args> = are the arguments to be passed to <program>.
<event>
The maximum number of events is 64. An event description should contain one or more of the
following definitions.
Definition Description
[hh:mm-hh:mm]
Time period.
time( h(...)
m(...) s(...) )
Time(hours, minutes, seconds).
[dd/mm-dd/mm]
Date period.
date( w(...)
m(...) d(...) )
Date(day, month, date).
pattern( (...)
(...) ... )
External events (e.g. alarms, motion detection).
Once
Start only once.
immune
Never interrupted.
Time and Date values are given as a list of values (separated by commas) and/or intervals
(separated by minus signs):
Hour = 0-23
Minute = 0-59
Seconds = 0-59
Day of the week = 0-6 (0 = Sunday)
Month = 1-12
Date = 1-31.
Patterns are defined as strings and follow the specific format <Client>:<Data>;
<Client>
If the client application sends <Data> to utask, the Data must be atomic, i.e. if the client wants
to notify two events at the same time, it must write:
<Client>:<Data1>;<Client>:<Data2>;.
Patterns are read by utask from /tmp/utasksocket. Utask can start a maximum of five (5)
child processes. When the maximum number of child processes has been exceeded, utask must
decide how to proceed. The process with the lowest priority (if the pending task has a higher
priority than this process) will then be killed. The entries in the configuration file (task.list)
are ordered by ascending priority, i.e. later entries precede earlier entries.