For my PHYSICAL port monitoring needs , I use an opensource project 
 Called catci.  I find the cacti forum(s) format far superior
 To mailing list format.. The forum is well laid out and may serve
 As a template if you wish to go this route . Cacti is an excellent
 Example of an opensource NMS project with contributed plugins and 
 Generous community support/contribution. 
                  http://forums.cacti.net/
  


--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or 
otherwise legally protected. It is intended only for the addressee. If you 
received this e-mail in error or from someone who was not authorized to send it 
to you, do not disseminate, copy or otherwise use this e-mail or its 
attachments.  Please notify the sender immediately by reply e-mail and delete 
the e-mail from your system.


-----Original Message-----

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Werner
Schram
Sent: Thursday, September 11, 2008 6:04 AM
To: nfsen-discuss@lists.sourceforge.net
Subject: [Nfsen-discuss] plugin repository and alert examples

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

It has been a while since I proposed to set up a plugin repository, but
I finally set something up :) The project can be found at:

http://sourceforge.net/projects/nfsen-plugins

I used the wiki function of sourceforge to provide a simple description
of the plugins. This is accessible from:

http://nfsen-plugins.wiki.sourceforge.net

The wiki isn't shown on the frontpage of the project, but according to
bugreport #2038132 the people at sourceforge are working on that.

I also created a mailing list to facilitate questions and public
discussion about plugins at:

http://sourceforge.net/mail/?group_id=235051

The plugins currently on the site are a botnet detection plugin and two
plugins to facilitate that plugin. So that isn't terribly much, but I
will be providing more myself in the future. If people are interested in
sharing their plugins in this project, just drop me a message, and I'll
add them to the project so they can do maintain their own portion of the
svn tree, do their file releases and manage their wiki pages.

I like the idea of Michael Donnelly about creating a place to share
alert examples. I think it might be a good idea to take it a bit broader
and call it nfsen usage examples or something of the like. I could
provide for it on the nfsen-plugins project, but the nfsen project
itself might be a better place. As usage examples aren't specifically
related to plugins. Does anybody have any thoughts about that? And about
the medium to share this information? Is a mailing list sufficient? or a
forum? or a wiki?

Regards,
Werner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjI7QoACgkQ3ULkMS4OADl6dgCgsQkrsCsGO1N5eywQwi/IIS7O
dnIAoPYvk1zgJapW2+Iy5k7lWTbgAWMI
=dbyj
-----END PGP SIGNATURE-----

------------------------------------------------------------------------
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Nfsen-discuss mailing list
Nfsen-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss

Reply via email to