Dimitri Arrigoni SwagDevOps

When should you use DateTime and when should you use Time?

It's a common misconception that [William Shakespeare][1] and [Miguel de Cervantes][2] died on the same day in history - so much so that UNESCO named April 23 as [World Book Day because of this fact][3]. However because England hadn't yet adopted [Gregorian Calendar Reform][4] (and wouldn't until [1752][5]) their deaths are actually 10 days apart. Since Ruby's Time class implements a [proleptic Gregorian calendar][6] and has no concept of calendar reform then there's no way to express this. This is where DateTime steps in:

>> shakespeare = DateTime.iso8601('1616-04-23', Date::ENGLAND)
=> Tue, 23 Apr 1616 00:00:00 +0000
>> cervantes = DateTime.iso8601('1616-04-23', Date::ITALY)
=> Sat, 23 Apr 1616 00:00:00 +0000

Debug your PHP in Docker with Intellij/PHPStorm and Xdebug

For your local dev, create a Dockerfile that is based on your production image and simply install xdebug into it. Exemple:

FROM php:5

RUN yes | pecl install xdebug \
&amp;&amp; echo "zend_extension=$(find /usr/local/lib/php/extensions/ -name xdebug.so)" &gt; /usr/local/etc/php/conf.d/xdebug.ini \

README

Services declared as oneshot are expected to take some action and exit immediatelly (thus, they are not really services, no running processes remain). A common pattern for these type of service is to be defined by a setup and a teardown action.

Let's create a example foo service that when started creates a file, and when stopped it deletes it.

Define setup/teardown actions

Create executable file /opt/foo/setup-foo.sh:

Fix `a stop job is running for session c2 of user xxx (xs / 1min 30s)`

This advice is pointing to arch based distributions. Manjaro in special

Install watchdog

# pacman -S watchdog >

How to change your commit messages in Git?

At some point you’ll find yourself in a situation where you need edit a commit message. That commit might already be pushed or not, be the most recent or burried below 10 other commits, but fear not, git has your back 🙂.

Not pushed + most recent commit:

git commit --amend

This will open your $EDITOR and let you change the message. Continue with your usual git push origin master.

NOTE

This content has moved.

Please go to bagder/TRRprefs for the current incarnation of the docs, and please help us out polish and maintain this documentation!

To limit a CPU to a certain C-state, you can pass the processor.max_cstate=X option in the kernel line of /boot/grub/grub.conf.

Here we limit the system to only C-State 1:

    kernel /vmlinuz-2.6.18-371.1.2.el5 ... processor.max_cstate=1

On some systems, the kernel can override the BIOS setting, and the parameter intel_idle.max_cstate=0 may be required to ensure sleep states are not entered:

	GRUB_DEFAULT=0
	# !!! GRUB_HIDDEN_TIMEOUT requires GRUB_TIMEOUT=0
	#GRUB_TIMEOUT=5
	GRUB_TIMEOUT=0
	GRUB_DISTRIBUTOR="Arch"
	# !!! add "intel_pstate=disable" to CMDLINE_LINUX_DEFAULT for no CPU sleeps (when NVidia freezes, bad drivers)
	# !!! blacklisting nouveau for better proprietary handling
	GRUB_CMDLINE_LINUX_DEFAULT="nouveau.blacklist=1 quiet sysrq_always_enabled=1"
	GRUB_CMDLINE_LINUX=""

	#!/bin/bash

	# Trap sigterm and sleep before passing signal to child for $SIGNAL_TIMEOUT seconds
	# this is to address a shutdown issue with traefik: https://docs.traefik.io/user-guide/marathon/#shutdown

	cmd=${*}
	# default to 10 seconds
	SIGNAL_TIMEOUT=${SIGNAL_TIMEOUT:-10}

	log() {

	package main

	import (
	"bufio"
	"net"
	"os"
	"syscall"
	)

	func println(msg string) {