Hi Marko, > Well to perform some tracking on the actual installation, I found the > git clone source in the .bash_history… > > root@Xxxx:~# grep -i 'git' .* > > .bash_history:git clone git://git.icinga.org/icinga-core.git > "git show" in the repository directory will give you the exact commit.
> So I can’t see how I actively chose a development source or anything > like that… > > root@Xxxx:~# grep -i 'github' .* > > root@Xxxx:~# > The master branch of the git repository holds the current development version. Even though quite some effort is put into making sure that the master can be built and used without problems you really shouldn't be using that for a production system as they haven't been as thoroughly tested as release versions: Stick to the release tarballs unless you're ready to debug weird problems. > And I can’t see how the relevance is between testing another version > will help when manually sending the command will be processed but not > the automatic with the exact same content? What are we looking for? > What step am I missing in the troubleshooting with the existing setup? > > I don’t have memory/cpu/harddrive space to spare to test more > variations without proper cause. It’s not like I can spare the time to > do another installation right off the bat either. Like you want me to > be more specific, I need to be specific to my superiors when I need to > explain **why** I’m spending so much time on this and I need to tell > them something besides “An internet dude wanted me to use your > hardware, licenses and consultant time to set up another machine. Why? > He hasn’t told me.” > Surely you must have some sort of test environment where you can safely test upgrades before deploying them to your production environment. Anyway, not really my call... just trying to give you a few hints as to how to use git. :) > //Marko V > Best regards Gunnar Beutner > > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > > > _______________________________________________ > icinga-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/icinga-users -- Gunnar Beutner Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nürnberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein | AG Nürnberg HRB18461 http://www.netways.de | [email protected] ** NETWAYS Open Source Monitoring Conference 2011 | Nürnberg, 29. und 30. November 2011 | http://www.netways.de/osmc ** ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ icinga-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/icinga-users
