Re: [Wrapper-user] Feature request: Script actions

[Leif M. <le...@ta...>]

Juergen,
    With all the related requests about this, it is actually a bit 
complicated.  The state
engine needs to be able to handle waiting for multiple external 
processes to complete.
I will give it some more thought.  I like your ideas here,

    There are a few related Feature Requests that are already open:
https://sourceforge.net/tracker/index.php?func=detail&aid=926800&group_id=39428&atid=425190
https://sourceforge.net/tracker/index.php?func=detail&aid=837037&group_id=39428&atid=425190

    I added this mail to first feature request.

Cheers,
Leif

Juergen Hermann wrote:

>Hi, it would be nice if one could start a script in 
>response to triggers, i.e.
>
>wrapper.filter.trigger.1=trigger string
>wrapper.filter.action.1=EXEC
>wrapper.filter.exechandler=/my/special/handling.sh
>
>This would then start the "exechandler" command with two 
>parameters:
> 1. The index of the trigger ("1")
> 1. The FULL log line that triggered the action.
>
>The return value of the script determines further action:
> 0 == NONE
> 1 == RESTART
> 2 == SHUTDOWN
>
>Use case is for example a clustered Tomcat installation, 
>where failure of one JVM might require restart actions for 
>the other JVMs too (or delaying of the restart for this 
>JVM, when the partner JVM is currently not available).
>
>Also, you could do things like active notification of 
>restarts via SNMP etc.
>
>
>
>Ciao, Jürgen
>
>--
>Jürgen Hermann, Developer
>WEB.DE AG, http://webde-ag.de/
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by:
>Power Architecture Resource Center: Free content, downloads, discussions,
>and more. http://solutions.newsforge.com/ibmarch.tmpl
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>