... | ... | @@ -21,7 +21,7 @@ Let's take an example with two applications registered: |
|
|
<application name="App2">
|
|
|
<start executable="/users/ics/app2"/>
|
|
|
<stop executable="kill" args="-2 $PID"/>
|
|
|
<error executable="/users/ics/error.sh" args="-debug"/>
|
|
|
<error executable="bash" args="/users/ics/error.sh -debug"/>
|
|
|
</application>
|
|
|
<applications>
|
|
|
</config>
|
... | ... | @@ -207,9 +207,10 @@ The variable *$PID* will be replaced by the PID of the running application. Howe |
|
|
|
|
|
If you need to define an error executable, you can for instance define:
|
|
|
```xml
|
|
|
<error executable="/users/ics/error.sh" args="-debug"/>
|
|
|
<error executable="bash" args="/users/ics/error.sh -debug"/>
|
|
|
```
|
|
|
If the running application terminates with an error the following arguments will be added to the command executed: *id*, *error code*, *current state*. For instance:
|
|
|
```
|
|
|
$ /users/ics/error.sh -debug 13 139 RUNNING
|
|
|
$ bash /users/ics/error.sh -debug 13 139 RUNNING
|
|
|
```
|
|
|
These information can be used to send a report by email. |
|
|
\ No newline at end of file |