them 'road worthy'. Even for early code I'd like to make sure they work g=
ood
Dan
On Sep 14, 2012, at 11:06 AM, O'Hara, Brad wrote:
> Dan,
>=20
> Will there be further announcement once they are available?
>=20
> Thanks,
> Brad
>=20
> -----Original Message-----
> From: Daniel Wittenberg [mailto:[email protected]]=20
> Sent: Thursday, September 13, 2012 6:53 PM
> To: Nagios Developers List
> Cc: ; [email protected]
> Subject: Re: [Nagios-devel] Nagios 4: Call for testing
>=20
> RPM's for CentOS/RHEL 6 will be available tomorrow. Shout if you want th=
em built for other platforms and I'll see what I can do.
>=20
> Dan
>=20
>=20
> On Sep 13, 2012, at 5:00 PM, Andreas Ericsson wrote:
>=20
>> Yes, you read it right. Nagios 4 is approaching, but it needs your=20
>> help to reach the finish-line, so pretty please HELP!
>>=20
>> Right now, config parsing is a lot quicker. Check execution is done=20
>> through workers, except on-demand host chekc execution, which is still=20
>> handled by the serial model.
>>=20
>> Code can be fetched from either of:
>> svn co https://nagios.svn.sourceforge.net/svnroot/nagios nagios=20
>> git://github.com/ageric/nagios.git
>>=20
>> The people who provide me with the most valuable bug reports will be=20
>> rewarded with a special prize, apart from a special mention at the=20
>> Nagios World Conference 2012, happening in Minneapolis on september=20
>> 25, 26, 27 and 28 this year (as it's 2012...).
>>=20
>> Points will be given on:
>> * Accuracy of bugreport. If the bug is triggered by one of 13 trillion =
=20
>> serviceescalations, you'll have an excellent chance if you produce an=20
>> example config which reproduces the problem without creating a huge=20
>> overhead.
>> * Patchiness of bugreport. If the bug contains valgrind output showing =
=20
>> illegal memory access, or a backtrace of the error, it will be given =20
>> extra credit. If it contains a minimal setup displaying the error as =20
>> well as a patch fixing the error, you're almost sure to be in the =20
>> very small Circle Of Winners.
>> * Surgeonry of bugreport. If a patch fixes a billion unrelated items, =20
>> points will be taken from it.
>> * bugreports of a slow Nagios accompanied by gprof or valgrind output =20
>> output will be given priority over other bugreports of a slow Nagios.
>>=20
>>=20
>> Note that only bugreports providede *before* 2012-09-24 will be=20
>> considerered, and also note that the winners will be announced at the=20
>> Nagios World Conference 2012 (unless they explicitly ask me not to=20
>> mention their names, in which case they can't even compete, really,=20
>> but will probably get several shots from me if I ever meet them and=20
>> *may* get a very special prize anyway).
>>=20
>>=20
>> Patches can be provided for Core Nagios, Livestatus, NDOUtils, Merlin=20
>> mod_gearman, dnx_utils or npcdmod. Each project gives extra points,=20
>> provided it's universal. Patches that promote a specific installation=20
>> directory are worthless and won't be considered.
>>=20
>>=20
>> So spedang! and get your hack on, folks
>>=20
>>=20
>> --=20
>> Andreas Ericsson [email protected]
>> OP5 AB www.op5.se
>> Tel: +46 8-230225 Fax: +46 8-230231
>>=20
>> Considering the successes of the wars on alcohol, poverty, drugs and=20
>> terror, I think we should give some serious thought to declaring war=20
>> on peace.
>>=20
>> ----------------------------------------------------------------------
>> --------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and=20
>> threat landscape has changed and how IT managers can respond.=20
>> Discussions will include endpoint security, mobile security and the=20
>> latest in malware threats.=20
>> http://www.accelacomm.com/jaw/sfrnl0424 ... /50122263/
>> _______________________________________________
>> Nagios-
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]