enricofoltran

package main

import (
	"context"
	"flag"
	"fmt"
	"log"
	"net/http"
	"os"
	"os/signal"

savishy

Vagrant and Hyper-V: Working with Virtual Network Interfaces

References

• Working with Vagrant and Hyper-V
• Vagrant Hyper-V Provider
• Creating an external virtual switch in hyper-v
• What to do if Hyper-V Manager is not found
• DockerNAT prevents other internal interfaces from working

anthonyclarka2

#!/bin/sh
# Enhanced backup script
# Sends messages to Zabbix based on exit code of borg executable
#
# anthonyclark AT G MAIL
# Shellcheck will still kvetch at you if notices are enabled
#
# This script will not work AS-IS but is only provided as such
# NO WARRANTIES
# This work is licensed under a Creative Commons Attribution 4.0 International License.

jrryjcksn

#!/bin/bash
# A bash script that will periodically checkpoint a container, maintaining a maximum of five checkpoints.
# Once five checkpoints have been created, it will periodically replace the oldest checkpoint with a new one.
# Arguments:
# - run_args (a single string containing the arguments to pass to 'docker run')
# - container_name (name of the existing container to run with automatic persistence or name to give to new container)
# - container_image (image to run in the container)
# - container_args (arguments to pass to the service running in the container)

run_args=$1

Madsy

How to build wine2.9 staging which supports Blizzard's Overwatch

Overview

gamax92's wine repo has the DirectX11 overwatch patches already applied. We need to build this version of Wine with WOW64 support. That is, the 64-bit version of wine which also supports 32-bit Windows programs. In so many words: if your CPU is 32-bit only, don't bother and you couldn't run Overwatch anyway.

Building wine with WOW64 support requires boostrapping the final build. The three stages look like:

1. Build the 64-bit version of wine (pass --enable-win64 to ./configure)

max-mapper

mjdietzx

#!/bin/bash

# install CUDA Toolkit v8.0
# instructions from https://developer.nvidia.com/cuda-downloads (linux -> x86_64 -> Ubuntu -> 16.04 -> deb (network))
CUDA_REPO_PKG="cuda-repo-ubuntu1604_8.0.61-1_amd64.deb"
wget http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/${CUDA_REPO_PKG}
sudo dpkg -i ${CUDA_REPO_PKG}
sudo apt-get update
sudo apt-get -y install cuda

bbengfort

package noplog

import "log"

var noplog = &NopLogger{
	log.New(NullWriter(1), "", log.LstdFlags),
}

// NullWriter implements the io.Write interface but doesn't do anything.
type NullWriter int

colophonemes

CREATE TRIGGER person_notify AFTER INSERT OR UPDATE OR DELETE ON income
FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
  'id',
  'email',
  'username'
);

CREATE TRIGGER income_notify AFTER INSERT OR UPDATE OR DELETE ON income
FOR EACH ROW EXECUTE PROCEDURE notify_trigger(
  'id',

RichardHightower

In this example, we are using Centos7, journalctl and systemctl so that we can monitor logs from DC/OS instances (masters, agents and public agents). It is useful for anyone using systemd, journald in an AWS EC2 enviroment that wants logging. The nice thing about Amazon CloudWatch is that it integrates well with Amazon EMR and Amazon Elasticsearch. (For more background on this subject see this article which covers using CloudFormation, Packr, etc. for Immutable Infrastructure to build DC/OS and deploy it to Amazon Web Services.)

We will install journald-cloudwatch-logs. We are going to setup a daemon into systemd that forwards logs to Amazon CloudWatch log streams.

This utility ***journald-cloudwat