Will there be an option in the future to have a yellow & red clock offset threshold ? presently there only seems to be a yellow threshold.
Thank you, ~Steve
There's an option in hobbit-clients.cfg:
CLOCK maximum-offset
If the system clock of the client differs from that of the
Hobbit
server by more than "maximum-offset" seconds, then the CPU
status
column will go yellow. Note that the accuracy of this test is
limited,
since it is affected by the time it takes a client status
report to
go from the client to the Hobbit server and be processed. You
should
therefore allow for a few seconds (5-10) of slack when you
define
your max. offset.
It is not wise to use this test, unless your servers are
synchronized
to a common clock, e.g. through NTP.
Hope is useful.
RB
On 9/17/07, s_aiello at comcast.net <s_aiello at comcast.net> wrote:
Will there be an option in the future to have a yellow & red clock offset threshold ? presently there only seems to be a yellow threshold.
Thank you, ~Steve
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Mon, Sep 17, 2007 at 11:08:00AM -0400, s_aiello at comcast.net wrote:
Will there be an option in the future to have a yellow & red clock offset threshold ? presently there only seems to be a yellow threshold.
It will only go yellow, because the test is not very accurate - it depends on the communication between the client and the server, and also on whether the Hobbit server has OK time or not.
Regards, Henrik
On Monday 17 September 2007, Henrik Stoerner wrote:
On Mon, Sep 17, 2007 at 11:08:00AM -0400, s_aiello at comcast.net wrote:
Will there be an option in the future to have a yellow & red clock offset threshold ? presently there only seems to be a yellow threshold.
It will only go yellow, because the test is not very accurate - it depends on the communication between the client and the server, and also on whether the Hobbit server has OK time or not.
Yes, I understood that. I am not performing +- 5 second checks, but more like +- 150 (yellow) +- 300 (red) checks. So in my scenario, I think there is plenty of buffer time for client/server communication issues.
participants (3)
-
henrik＠hswn.dk
-
mailinglistbh＠gmail.com
-
s_aiello＠comcast.net