I have followed the guide
http://www.opennms.org/index.php/HostResourcesSwRunMonitor to check
proccesses, everything seems to be ok, because opennms discovers the
proccess, but when the proccess is down, in opennms still seems to be up.
I'm using opennms 1.6
this is the capsd configuration
<protocol-plugin protocol="Amarok"
class-name="org.opennms.netmgt.capsd.plugins.LoopPlugin" scan="on"
user-defined="false">
<protocol-configuration scan="enable" user-defined="false">
<specific>192.168.0.101</specific>
<property key="timeout" value="2000" />
<property key="retry" value="1" />
</protocol-configuration>
</protocol-plugin>
and this is the poller confifuration
<service name="Amarok" interval="300000" user-defined="false"
status="on">
<parameter key="retry" value="1"/>
<parameter key="timeout" value="3000"/>
<parameter key="service-name" value="amarokapp"/>
</service>
<monitor service="Amarok"
class-name="org.opennms.netmgt.poller.monitors.HostResourceSwRunMonitor"/>
thanks
henry
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
