Hi, again. After a small dicuss with naparuba, it seems that the best thing to do is to remove all the nagios plugin compiled from the windows libexec folder and open a new repository/foler/zip/... to share them. So i will do that. It's OK for the IT Admins, but not for the "only-windows" users. My questions are :
No problems to manage that in an scripted install but do i leave only my devs (WMIC.EXE) and the scripts in the branch - including the sources of the .exe to be compliant with the AGPL. In this case How to manage the SETUP.EXE in the windows world. Windows users are not agree with a lot of pre-requisites witch are not included in the master package. But if i deliver this type of setup.exe i am not compliant with the 3rd part products and their licences.... Not very easy ! I will also have to manage a type of wget to retrieve check_wmi_plus.pl and modify all the conf files.... And last, it's not possible - or very difficult ? to include the nagios plugins, because i only found the sources, and i have to install cygwin to compile them - and the check_nt to have something working on my windows 2008. The side by side zip file is a solution, but what about licences ? One another solution is to forget the nagios plug-ins to only use check_wmi_plus... the fastest choice :-) How is you opinion about this windows side of shinken project ? I am ready to discuss all the possible choices. and deliver the right choice choosen by the community. Jean-François BUTKIEWICZ Consultant VEOSOFT (groupe VEONERGIE) ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
