Windows installation for shinken, using .net services instead of instsrv... #644

Closed
wants to merge 2 commits into
from

Conversation

Projects
None yet
2 participants
Contributor

jfbutkiewicz commented Oct 25, 2012

....

Added some batch files to stop/start services and configuring the use of check_wmi_plus.pl
Modifications on the conf files to be installation path independent.

Touch only the windows systems.

regards.
JFB

@jfbutkiewicz jfbutkiewicz Windows installation for shinken, using .net services instead of inst…
…srv.

Added some batch files to stop/start services and configuring the use of check_wmi_plus.pl
Modifications on the conf files to be installation path independent.
6ff7ca2

@naparuba naparuba and 1 other commented on an outdated diff Oct 25, 2012

windows/install-shinken.cmd
+rem (c) 2012 October, By VEOSOFT, Jean-françois BUTKIEWICZ
+rem This script is for IT admins only. If you do not have experience or
+rem knowledge fundation to install manually shinken on a windows host, please use the
+rem integrated installation of Shinken using the setup.exe program delivered by
+rem VEOSOFT. This kind of installation perform the same tasks but without any request
+rem using command line.
+rem This script is delivered upon Alfresco GPL licence.
+rem
+
+echo Shinken Windows Installation
+echo Provided by VEOSOFT for Shinken Team
+echo V 1.2 - October 2012
+echo ====================================
+echo Checkin for InstallUtil tool ....
+
+if exist "%systemroot%\microsoft.net\framework\v2.0.50727\installutil.exe" goto NEXTSTEP1
@naparuba

naparuba Oct 25, 2012

Owner

It it normal that a specific version is used here? What about other versions of this tool?

@jfbutkiewicz

jfbutkiewicz Oct 25, 2012

Contributor

Hi,

in fact there are 4 versions of this tool, 2 with the 2.0 version (32 and 64 bits) and 2 on the 4.0 Client.
I am based on a standard 2008 Windows installation witch is provied with the .net 3.5 (formelly an extention of the 2.0 version) A standard installation (or an uptodate windows) has this folder. So  this is the standard path. I used the 32 bit to touch the most of computers (including workstations)
I don't have the way to check whitch .net version is installed - for the moment but i can search.
It's also the case on an XP, Vista and Seven installation. This path never change for the moment.  

With the libexec folder, i can delete all the check_xx programs and the DLL of my compiled cygwin version. With this version only the local check swap is used an all the others check are set by the check_wmi_plus templates.
WMIC.EXE is my own work, it's under AGPL.

Let me know if you want to delete the libexec 3 part files.
regards,

Jean-François BUTKIEWICZ
Consultant VEOSOFT (groupe VEONERGIE)

----- Mail original -----

De: "Gabès Jean" notifications@github.com
À: "naparuba/shinken" shinken@noreply.github.com
Cc: "jfbutkiewicz" jean-francois.butkiewicz@veosoft.net
Envoyé: Jeudi 25 Octobre 2012 10:23:15
Objet: Re: [shinken] Windows installation for shinken, using .net services instead of instsrv... (#644)

In windows/install-shinken.cmd: > +rem (c) 2012 October, By VEOSOFT, Jean-françois BUTKIEWICZ

+rem This script is for IT admins only. If you do not have experience or
+rem knowledge fundation to install manually shinken on a windows host, please use the
+rem integrated installation of Shinken using the setup.exe program delivered by
+rem VEOSOFT. This kind of installation perform the same tasks but without any request
+rem using command line.
+rem This script is delivered upon Alfresco GPL licence.
+rem
+
+echo Shinken Windows Installation
+echo Provided by VEOSOFT for Shinken Team
+echo V 1.2 - October 2012
+echo ====================================
+echo Checkin for InstallUtil tool ....
+
+if exist "%systemroot%\microsoft.net\framework\v2.0.50727\installutil.exe" goto NEXTSTEP1
It it normal that a specific version is used here? What about other versions of this tool?

Reply to this email directly or view it on GitHub .

Owner

naparuba commented Oct 25, 2012

Thanks for the patch.

But we should move all libexec checks to another package/repository because lot of theses checks are classic ones, and we got no interest into "forking" them in the Shinken root tree. (with their dll too of course)

We can open a new repository if you want for them, or put them in the website as a zip file maybe. I think with some of them we can even have some license problem (shinken is in affero GPL, lot are GPLv2 and maybe not v2+).

I'm not sure putting all in the shinken tree for libexec is a good thing, we can talk about it in the mailing list.

@jfbutkiewicz jfbutkiewicz According with the shinken owner, removing the libexec third part of …
…the shinken sources.

Modification of the windows installation script to download the thirdpart from veosoft. Adding the sources of wget and wmic programs to match the agpl v3 license. adding the dounzip script to unzip the thirdpart without external program (no command line on windows to do that). Another time compliance with the agpl to use only other agpl programs into the source folder (or only use other programs, but in the windows world, the others tools are not given or in a license mode not directly compatible ith the agpl one) and display the sources. My main goal is to use a realy out of the box usable script....
dc31998
Contributor

jfbutkiewicz commented Nov 4, 2012

Hi, i modify the libexec as we discussed by e-mail. Maybe the install-shinken.cmd can be improved, but it is working - It's a first step. Let me know if it is matching your concept of shinken for windows. The libexec and check_wmi_plus modified for shinken are actually stored on veosoft.net.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment