Heads up for config changes in Nagios 4

[Andreas Ericsson]

On 08/31/2012 04:06 AM, Yu Watanabe wrote:
> First time hearing about Nagios 4.
> 
> Is it coming out soon?
> 

In a couple of weeks is the general idea. People are alpha testing it
already, but some more longtime tests are required before it goes
live, and for full-on production use (with no other systems doing
automated checking), I'd wait until Nagios 4.0.1, when we've ironed
out any remaining bugs that we missed in testing.

op5 will do a release based on Nagios 4 in december, so I'll have
bugfixing the core as my top priority from the release until then.
Because of that, it's likely 4.0.1 will be out before christmas.
Unless 4.0 happens to be bugfree ofcourse. Not impossible, but very
unlikely with 20k lines added and 30k lines removed.

In the meantime, testing of config parsing and the new check engine
is ofcourse very helpful. I'd prefer to get anomaly-reports on mail
to nagios-devel, with ae at op5.com on the cc-list so I don't miss out
on anything serious.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null