Xymon Mailing List Archive search

Updated post-RC6 patch

2 messages in this thread

list Henrik Størner · Mon, 28 Mar 2005 12:46:51 +0200 ·
Folks,

I found a problem with the disk report handler in the post-RC6 patch -
it could get stuck in an infinite loop, due to a bug I introduced when
trying to add support for AS/400 disk reports.  If you're bitten by
this, you'll have a hobbitd_larrd proces that is just spinning like
mad, burning cpu time but doing absolutely nothing (so no graph
updates).

I have updated the post-RC6 patch with a proper way of handling this.

If you applied the original post-RC6 patch, back it out with:

   cd hobbit-4.0-RC6
   patch -R -p1 </tmp/post-RC6.patch

Then apply the new one:

   cd hobbit-4.0-RC6
   patch -p1 </tmp/post-RC6-v2.patch

Then run "make clean; make", stop Hobbit and run "make install", then
start Hobbit again.

This also includes a couple of other fixes, including one where
removing a host from the bb-hosts file could cause it to get "stuck"
in Hobbit as purple, with no way of removing the host (except stopping
and starting Hobbit); and an improvement so you can list multiple
week-days in time-specifications for alerts, downtime etc.


Regards,
Henrik
list David Stuffle · Mon, 28 Mar 2005 14:07:13 -0500 ·
quoted from Henrik Størner
Henrik Stoerner wrote:
and an
improvement so you can list multiple week-days in
time-specifications for alerts, downtime etc.
Thanks a ton, Henrik!  This makes my rules much easier!!

~~~~~~~~~~~~~~
David Stuffle
Delta Faucet Company


This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
Please note that any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the company.
Finally, the recipient should check this email and any attachments for the
presence of viruses. The company accepts no liability for any damage caused
by any virus transmitted by this email.