mod_response

Whenever a vital changes status, mod_response executes response handlers provided by the administrator to handle the change and take any necessary, predefined action.

Handlers for the network are arranged in a specially designed file tree. It's basic structure involves a directory for each node, with sub directories for each vital and then the response handler executables. As an example, here is a simple response handler tree:

/192.168.0.2/http/normal
/192.168.0.2/http/warning
/192.168.0.2/http/fatal
/192.168.0.2/ping/alive
/192.168.0.2/ping/dead
/192.168.0.7/ping/alive
/192.168.0.7/ping/dead
    

Each of the handlers are executes whenever that vital enters the status with the handlers name. All text in these cases is lower case, to avoid any ambiguities. It's up to you, as the administrator, what goes on inside of these. Oh, and please don't send e-mails from them.

Warning

mod_response is a major work in progress and an idealogical kink in my neck. While developing State, I always intended for her to be passive. I never imagined or intended State to go around trying to fix things on its own. The whole scenario is just to SkyNet like for me. It is useful for some people though, so I digress.