[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
monit monit.pod
From: |
Jan-Henrik Haukeland |
Subject: |
monit monit.pod |
Date: |
Sat, 30 Nov 2002 10:55:13 -0500 |
CVSROOT: /cvsroot/monit
Module name: monit
Changes by: Jan-Henrik Haukeland <address@hidden> 02/11/30 10:55:13
Modified files:
. : monit.pod
Log message:
I have taken the liberty to change the documentation a bit. I'm
wondering about
this:
This way hearbeat can easily control the cluster state and if one
node fails, hearbeat will start monit-xxxxx on the failing node
=> monit is instructed to start the services of the failing node
and monitor them...
Shouldn't it say:
This way hearbeat can easily control the cluster state and if one
node fails, hearbeat will start monit-xxxxx on the running node
=> monit is instructed to start the services of the running node
and monitor them...
Ps. martin the timestamp functionality looks cool and can be used for
some
neat trick
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/monit/monit/monit.pod.diff?tr1=1.40&tr2=1.41&r1=text&r2=text