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
So I can't see how I actively chose a development source or anything like
that...
root@Xxxx:~# grep -i 'github' .*
root@Xxxx:~#
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."
//Marko V
------------------------------------------------------------------------------
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
