Where can I locate the snapshots? I must be blind again! :(
Jason Chambers IT Helpdesk Support Geosoft Inc. 85 Richmond St. West - 8th Floor Toronto, Ontario, Canada M5H 2C9 Tel: 416-369-0111 x344 Fax: 416-369-9599 www.geosoft.com
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Sunday, November 13, 2005 5:36 AM To: hobbit at hswn.dk Cc: hobbit-announce at hswn.dk Subject: [hobbit] Hobbit 4.1.2p1 available
Some of you have already noticed that I put a 4.1.2p1 "patch 1" release up for download on my Hobbit demo-site. It is hereby officially released and available via Sourceforge.
As the version number indicates, this is solely a bug-fix release for 4.1.2. I am working on some new stuff, but you won't find it in this release (if you're interested, get the snapshots instead).
This release fixes a number of bugs in Hobbit 4.1.2, some of which could cause parts of Hobbit to crash; it also changes how alerts are handled when a status goes green->yellow->red.
Updating is recommended.
Changes from 4.1.2 -> 4.1.2p1 (10 Nov 2005)
Bugfixes:
- hobbitd could crash when processing a "combo" message, due to an incorrect test of the color of one message inside the combo-message before that color was actually deciphered.
- hobbitd_alert would crash when attempting to save a checkpoint while cleaning up a "dead" alert.
- Disk graphs would show up with all graphs in a single image, when the status message included any colored icons (typically, when the status was red or yellow).
- The handling of alerts was counting the duration of an event based on when the color last changed. This meant that each time the color changed, any DURATION counters were reset. This would cause alerts to not go out if a status was changing between yellow and red faster than any DURATION setting. Changed this to count the event start as the *first* time the status went into an alert state (yellow or red, usually).
- An idle hobbitd process would accumulate zombie processes.
Improvements:
- When a status goes yellow->red, the repeat-interval is now cleared for any alerts. This makes sure you get an alert immediately for the most severe state seen. This only affects the first such transition; if the status later changes between yellow/red, this normal REPEAT interval applies.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Regards Lars
----- Original Message ----- From: "Jason Chambers" <Jason.Chambers at geosoft.com> To: <hobbit at hswn.dk> Sent: Tuesday, November 15, 2005 4:02 PM Subject: RE: [hobbit] Hobbit 4.1.2p1 available
Where can I locate the snapshots? I must be blind again! :(
Jason Chambers IT Helpdesk Support Geosoft Inc. 85 Richmond St. West - 8th Floor Toronto, Ontario, Canada M5H 2C9 Tel: 416-369-0111 x344 Fax: 416-369-9599 www.geosoft.com
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Sunday, November 13, 2005 5:36 AM To: hobbit at hswn.dk Cc: hobbit-announce at hswn.dk Subject: [hobbit] Hobbit 4.1.2p1 available
Some of you have already noticed that I put a 4.1.2p1 "patch 1" release up for download on my Hobbit demo-site. It is hereby officially released and available via Sourceforge.
As the version number indicates, this is solely a bug-fix release for 4.1.2. I am working on some new stuff, but you won't find it in this release (if you're interested, get the snapshots instead).
This release fixes a number of bugs in Hobbit 4.1.2, some of which could cause parts of Hobbit to crash; it also changes how alerts are handled when a status goes green->yellow->red.
Updating is recommended.
Changes from 4.1.2 -> 4.1.2p1 (10 Nov 2005)
Bugfixes:
- hobbitd could crash when processing a "combo" message, due to an incorrect test of the color of one message inside the combo-message before that color was actually deciphered.
- hobbitd_alert would crash when attempting to save a checkpoint while cleaning up a "dead" alert.
- Disk graphs would show up with all graphs in a single image, when the status message included any colored icons (typically, when the status was red or yellow).
- The handling of alerts was counting the duration of an event based on when the color last changed. This meant that each time the color changed, any DURATION counters were reset. This would cause alerts to not go out if a status was changing between yellow and red faster than any DURATION setting. Changed this to count the event start as the *first* time the status went into an alert state (yellow or red, usually).
- An idle hobbitd process would accumulate zombie processes.
Improvements:
- When a status goes yellow->red, the repeat-interval is now cleared for any alerts. This makes sure you get an alert immediately for the most severe state seen. This only affects the first such transition; if the status later changes between yellow/red, this normal REPEAT interval applies.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (2)
-
Jason.Chambers＠geosoft.com
-
lars.ebeling＠leopg9.no-ip.org