Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

{% if grains['os_family'] == 'RedHat' and grains['osmajorrelease'][0] == '7' %}
include:
- .docker
/etc/sysconfig/selinux:
file.replace:
- pattern: SELINUX=enforcing
- repl: SELINUX=permissive
$ cat ~/.ssh/config
Host *
ForwardAgent yes
ForwardX11 yes
ForwardX11Trusted yes
Compression yes
ControlMaster auto
ControlPath /tmp/ssh_mux_%h_%p_%r
ControlPersist 4h
TCPKeepAlive no
diff --git a/src/haproxy-systemd-wrapper.c b/src/haproxy-systemd-wrapper.c
index e588af9..bfce4e6 100644
--- a/src/haproxy-systemd-wrapper.c
+++ b/src/haproxy-systemd-wrapper.c
@@ -60,6 +60,8 @@ static void locate_haproxy(char *buffer, size_t buffer_size)
return;
}
+static int read_pids(char ***pid_strv);
+
When reloading haproxy too fast on EL7 (RedHat, CentOS) the system is
being filled with orphaned processes.
I encountered this problem on CentOS 7 with
haproxy-1.5.4-4.el7_1.x86_64 but expect it to exist on all systems
using haproxy-systemd-wrapper not just those based on Fedora.
Steps to reproduce:
1) haproxy is running normal.
#!/bin/bash
dnf install autoconf automake cmake freetype-devel gcc gcc-c++ git libtool make mercurial nasm pkgconfig zlib-devel
mkdir ~/ffmpeg_sources
cd ~/ffmpeg_sources
git clone --depth 1 git://github.com/yasm/yasm.git
cd yasm
autoreconf -fiv
./configure --prefix="$HOME/ffmpeg_build" --bindir="$HOME/bin"
make
make install
#!/bin/bash
set -e -o nounset -o pipefail
# Credentials for user EBSbackup
# with inline policy that allows:
# ec2:CreateSnapshot
# ec2:CreateTags
# ec2:DeleteSnapshot
# ec2:DescribeSnapshots
# ec2:DescribeVolumes
@lloesche
lloesche / update-network-folder-view.scpt
Created May 31, 2016 08:12
Update OSX Finder View (refreshes changed content on network/smb shares)
tell application "Finder" to tell front window to update every item
Dockerfile:
FROM alpine:edge
CMD ["Hello World"]
ENTRYPOINT ["echo"]
{
"id": "/marathon-test",
"instances": 1,
"container": {
@lloesche
lloesche / gist:a99e9e487f7bdc3b59c14c2c5ee4a25d
Created June 27, 2017 11:30
Testing our Github credential leakage scanner
[default]
aws_access_key_id = AKIAJQATOQGMX2TOF1CX
aws_secret_access_key = I3rNML6Nl0vPbh0CuQdqSQ3LB5kHYAaBrWd+VEho
(these are invalid credentials)
@lloesche
lloesche / nvmelink.py
Created April 17, 2018 14:33
Create symlinks for AWS EC2 nvme devices