John jhn--

Sample service script for debianoids

Look at LSB init scripts for more information.

Usage

Copy to /etc/init.d:

# replace "$YOUR_SERVICE_NAME" with your service's name (whenever it's not enough obvious)

Linux simple performance tweaks

Change the I/O Scheduler

Open $ vim /etc/default/grub then add elevator=noop next to GRUB_CMDLINE_LINUX_DEFAULT. Run $ update-grub and $ cat /sys/block/sda/queue/scheduler to be sure that noop is being used:

$ vim /etc/default/grub
$ update-grub
$ cat /sys/block/sda/queue/scheduler

[noop] deadline cfq

Installing Kerberos on Redhat 7

This installation is going to require 2 servers one acts as kerberos KDC server and the other machine is going to be client. Lets assume the FQDN's are (here cw.com is the domain name, make a note of the domain name here):

Kerberos KDC Server: kdc.cw.com
Kerberos Client: kclient.cw.com

Important: Make sure that both systems have their hostnames properly set and both systems have the hostnames and IP addresses of both systems in

Directory structure for JavaScript/Node Projects

While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.

Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.

Directories

lib/ is intended for code that can run as-is
src/ is intended for code that needs to be manipulated before it can be used

	#!/bin/bash

	if [[ "$#" < "2" \|\| "$#" > "3" ]]; then
	cat <<END
	Glusterfs GFID resolver -- turns a GFID into a real file path

	Usage: $0 <brick-path> <gfid> [-q]

	<brick-path> : the path to your glusterfs brick (required)

	-module(barber).
	-export([run/2, barber/1, clients/1, simulator/2]).

	-define(CUT_DUTAION, 20).

	run(RoomSize, Duration) ->
	% create barber
	BPid = spawn(?MODULE, barber, [?CUT_DUTAION]),
	% run simulartor with barber PID
	SPid = spawn(?MODULE, simulator, [BPid, RoomSize]),

	# {{ ansible_managed }}

	# This file describes the network interfaces available on your system
	# and how to activate them. For more information, see interfaces(5).

	# The loopback network interface
	auto lo
	iface lo inet loopback

	{% if ansible_interfaces\|length > 2 %}

	---
	# This has been tested with ansible 1.3 with these commands:
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=false"
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts isFirstRun=true"
	# ansible-playbook -i hosts ansible_conditionals_examples.yaml --extra-vars="hosts=myhosts"
	# NB: The type of the variable is crucial!

	- name: Ansible Conditionals Examples
	hosts: $hosts
	vars_files:

	Step 1: Upgrade Packages
	# yum update
	# yum groupinstall "Development Tools"

	Step 2: Installing Recommended Packages
	# yum install gcc-c++ patch readline readline-devel zlib zlib-devel
	# yum install libyaml-devel libffi-devel openssl-devel make
	# yum install bzip2 autoconf automake libtool bison iconv-devel

	Step 3: Install RVM ( Ruby Version Manager )

	# Compiled source #
	###################
	*.com
	*.class
	*.dll
	*.exe
	*.o
	*.so

	# Packages #