[Nagiosplug-devel] Flight 1.4.8, ready for boarding

[Anthony Montibello]

Thanks for the responce,
I am not trying to push the issue, but I wanted to make sure I explained my
addition request.

I agree with the Client/server versions being kept together, and that is how
I have been distributing the source.

I am not very familiar with How or Where to publish a RFC, but I would be
happy to contribute to one. Is there anyone who can asssist in getting this
started?

I suggested including the newest version of check_nc_net (that I finished
this week) because of particular reasons:

   - It is fully compatible with the older check_nt, (I made only bug
   fixes to these checks that the original check_nt preforms) So for the
   commands offered in check_nt it will work with any server:
   NC_NEt,NS_Client,NS_Client++.
   - the new command (-v OTHER) that allows for issuing any command to
   the server side.
   - A more comprehensive help system by using --help=<-v command>  this
   gives help on the particular command.
   - It is easier to Nagios users that want to use any of the
   enhancements that NC_NEt offers, by already having the plugin compile with
   the Nagios Plugins. (while still preserving the old check_nt)
   - I also added a switch that allows for output to extend beyond the
   1249 bytes (for when server side has extended outputs)

once again, thank you for the responce.
I suggested its addition because I thought it would be benifit to Nagios
comunity.

Tony (Author of NC_Net)
tony at montitech.com






On 4/2/07, Ton Voon <ton.voon at altinity.com> wrote:
>
>
> On 30 Mar 2007, at 23:42, Anthony Montibello wrote:
>
> > I would like to submit check_nc_net.c to the plugins,
> > I was working on it this week and finally have it to a good enough
> > point.
> > Whats the procedure/best way to submit this,
> >
> > check_nc_net is the check_nt used for NC_Net with all the extended
> > commands and enhancements I added.
>
> What do other think about this?
>
> I wasn't entirely convinced when check_nt was added into the
> distribution, and similarly I'm not sure why check_nc_net should be
> added either. We don't include check_nrpe as part of the
> distribution, though we do include check_by_ssh, which is an "agent"
> type plugin.
>
> I think I'm worried that the client code needs to be kept in sync
> with the server code, so should be kept together. It doesn't help
> anyone if Nagios Plugins distributes old code.
>
> I'd be more comfortable if there was an RFC or some other published
> location that detailed what the comms between the client and server
> are. At least this says that there is some fixed standard, so then we
> can say that the one distributed by us is conforming to a particular
> version.
>
> That's probably the difference between check_by_ssh and check_nrpe/
> check_nt/check_nc_net - the interface for the agent communication is
> standardised.
>
> Ton
>
> http://www.altinity.com
> T: +44 (0)870 787 9243
> F: +44 (0)845 280 1725
> Skype: tonvoon
>
>
>
>
> -------------------------------------------------------------------------
> 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
> _______________________________________________________
> Nagios Plugin Development Mailing List
> Nagiosplug-devel at lists.sourceforge.net
> Unsubscribe at
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-plugins.org/archive/devel/attachments/20070402/0d11d1f8/attachment.html>