StoneBlog.stonesoft.com

Each time an event listed in the table below occurs, it is checked if the corresponding script specified in the table exists. If the script exists, a notification log message indicating script execution is produced. After that, the script is tried to be executed with the parameter(s) specified in the table. If the script can not be executed, if the script is terminated by a signal or if the script exits with a non-zero value, an error log message is produced. If the script is succesfully executed and it exits with zero value, another notification log message is produced after the script exits.

EVENT :: SCRIPT :: PARAMETER(S)

Node has been booted :: /data/run-at-boot :: (none)
Policy has been applied :: /data/run-at-policy-apply :: Id of the new configuration
Node enters “online” state :: /data/run-at-online :: Previous cluster status (1)
Node enters “locked-online” state :: /data/run-at-locked-online :: Previous cluster status (1)
Node enters “offline” state :: /data/run-at-offline :: Previous cluster status (1)
Node enters “locked-offline” state :: /data/run-at-locked-offline :: Previous cluster status (1)
Node enters “standby” state :: /data/run-at-standby :: Previous cluster status (1)

(1) One of the following strings:
- online
- locked-online
- offline
- locked-offline

written by RoarinPenguin - 1,301 views \\ tags: hooks, state transitions, stonegate firewall