Off to the Nagios Conference

[Einar Indridason]

On 9/21/06, Francois Caen <frcaen at gmail.com> wrote:
>
> On 9/19/06, Thomas Slutyer <nagios at kilala.nl> wrote:
> > In about twelve hours I'll jump in my car and drive for eight hours to
> > Nürnberg, Germania for the first annual Nagios Conference
> > (http://www.nagiosconference.de).
>
> Wow, the schedule looks really interesting. I can't wait for
> www.nagiosconference.us
> :-)



Sadly I didn't know about the Nagios conference, until just now.  I'm
curious... will the presentations be made available afterwards?  I would
like to know, for example, where Nagios 3.0 is headed, and how the interface
will be designed.  (Will it be more "Ajax"-like?)  Will Nagios 3.0 have a
"central information daemon", instead of the big status.dat file it
currently has?  Will we have a "libnagios" to do the gruntwork?  How are the
"broker" functions / functionality coming along?  Will we have various SQL
backends?  (MySQL / PostgreSQL / SQLite / ...)?  Etc.

So... if possible, please make the presentations available to those of us
poor souls, that can't make it to the conference.

Cheers,
--
EinarI
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060921/408599b2/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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