| {c="1;1"} | |
| /TCP_MISS/ { c="1" } | |
| /TCP_MEM_HIT/ { c="2;1" } | |
| /TCP_HIT/ { c="2" } | |
| /_UNMODIFIED/ { c="4" } | |
| /_ABORTED/ {c="4;1"} | |
| {print "\033[3"c"m"$0 "\033[0m"} |
| #!/bin/bash | |
| # Author: Thomas Mueller <thomas@chaschperli.ch> | |
| # Date: 2015-06-05 | |
| # enable to exit on first error | |
| # set -e | |
| # list gem's to create rpm's seperated by space | |
| # example for 2 gems: gem_list="r10k trocla" |
| LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-3.0.11/ext/apache2/mod_passenger.so | |
| PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.11 | |
| PassengerRuby /usr/bin/ruby | |
| <VirtualHost *:80> | |
| ServerName logs.example.com | |
| ServerAlias logs.example.com | |
| DocumentRoot /home/httpd/Kibana/static |
| 1. Generate a pre-signed certificate for client1.example.com with the following command: | |
| puppet cert --generate client1.example.com | |
| Puppet will now generate and sign a client certificate in the name of client1. example.com. | |
| 2. Transfer the three required files; the private key, the client certificate, and the CA certificate, to the new client. These are found in the following locations: | |
| /etc/puppet/ssl/private_keys/client1.example.com.pem | |
| /etc/puppet/ssl/certs/client1.example.com.pem | |
| /etc/puppet/ssl/certs/ca.pem | |
| Transfer these to the corresponding directories on the client, and it will then be authenticated without the certificate request step. Note that the location of Puppet's SSL certs varies according to the ssldir setting in puppet.conf. |
Locate the section for your github remote in the .git/config file. It looks like this:
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = git@github.com:joyent/node.git
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:
The intention is to get a clean build of MRI 1.8.7 and 1.9.3.
MRI 1.8.7 doesn't play nicely with LLVM based GCC compilers. In Mountain Lion, the only way to get a non-LLVM gcc is to build one yourself. The command line tools package in Xcode 4.4 does not contain a non-llvm based GCC.
| Quick gist on getting vsphere and vcenter and fog/vsphere going | |
| # Things to download | |
| - Download free evaluation version of window 2008 | |
| - Download free evaluation of esxi v5 | |
| - Download free evaluation of esxi vsphere (control center) iso | |
| # Install esxi in vmware fusion | |
| 1)Install esxi in vmware (select vmware/esx as host) | |
| create a user root/pipopopo |
| VERSION=5.4.1 | |
| DOWNLOAD=http://apache.cs.utah.edu/activemq/apache-activemq/$(VERSION)/apache-activemq-$(VERSION)-bin.tar.gz | |
| NAME=apache-activemq | |
| TARBALL=$(NAME)-$(VERSION)-bin.tar.gz | |
| BUILDDEPS= | |
| RUNDEPS=java-runtime | |
| #CFLAGS=-g | |
| .PHONY: default |