| # ######################################## | |
| # Start server and manager in background | |
| /start-server.sh & | |
| SERVER_PID=$! | |
| /start-manager.sh & | |
| MANAGER_PID=$! | |
| # ######################################## |
| DATA AND METADATA COHERENCE | |
| Some modern cluster file systems provide perfect cache coherence among their clients. Perfect cache coherence among disparate NFS clients is expensive to achieve, especially on wide area networks. As such, NFS settles for weaker cache coherence that satisfies the requirements of most file sharing types. | |
| Close-to-open cache consistency | |
| Typically file sharing is completely sequential. First client A opens a file, writes something to it, then closes it. Then client B opens the same file, and reads the changes. | |
| When an application opens a file stored on an NFS version 3 server, the NFS client checks that the file exists on the server and is permitted to the opener by sending a GETATTR or ACCESS request. The NFS client sends these requests regardless of the freshness of the file's cached attributes. | |
| When the application closes the file, the NFS client writes back any pending changes to the file so that the next opener can view the changes. This al |
| """ | |
| A simple proxy server, based on original by gear11: | |
| https://gist.github.com/gear11/8006132 | |
| Modified from original to support both GET and POST, status code passthrough, header and form data passthrough. | |
| Usage: http://hostname:port/p/(URL to be proxied, minus protocol) | |
| For example: http://localhost:5000/p/www.google.com | |
| """ | |
| import re |
| <?php | |
| /* | |
| * Plugin Name: Better errors | |
| * Description: Better errors in log | |
| * Author: Daniele Scasciafratte | |
| * Version: 1.0 | |
| * Author URI: http://codeat.co | |
| */ | |
| function handleError($code, $description, $file = null, $line = null, $context = null) { |
When setting these options consider the following:
sudo grep max_children /var/log/php?.?-fpm.log.1 /var/log/php?.?-fpm.log
| # -*- encoding: utf-8 -*- | |
| # requires a recent enough python with idna support in socket | |
| # pyopenssl, cryptography and idna | |
| from OpenSSL import SSL | |
| from cryptography import x509 | |
| from cryptography.x509.oid import NameOID | |
| import idna | |
| from socket import socket |
| # wp-secure.conf | |
| # | |
| # | |
| # This file includes common security considerations for wordpress using nginx. | |
| # | |
| # The goal is to block actions which are usually dangerous to wordpress. | |
| # Additionally, we block direct access to PHP files and folders which should not | |
| # be accessed directly from a browser. | |
| # | |
| # Also have included exceptions for plugins that are known to require this access. |
Let's say you have a SysV Init Script named foo
Copy the file to /etc/init.d/foo
Enable the SysV service: chkconfig --add foo
Enable the SysV service: chkconfig foo on
Start the service: service foo start. After this, systemd-sysv-generator will generate this file /run/systemd/generator.late/foo.service, copy this file to /etc/systemd/system by running: cp /run/systemd/generator.late/foo.service /etc/systemd/system/foo.service
Edit /etc/systemd/system/foo.service by running systemctl edit foo.service, add in the following line to foo.servie (this makes the service installable)
[Install]
| # No dupes | |
| export HISTCONTROL=ignoreboth:erasedups | |
| # Eternal bash history. | |
| # --------------------- | |
| # Undocumented feature which sets the size to "unlimited". | |
| # http://stackoverflow.com/questions/9457233/unlimited-bash-history | |
| export HISTFILESIZE= | |
| export HISTSIZE= | |
| export HISTTIMEFORMAT="%F %T " |
Many different applications claim to support regular expressions. But what does that even mean?
Well there are lots of different regular expression engines, and they all have different feature sets and different time-space efficiencies.
The information here is just copied from: http://regular-expressions.mobi/refflavors.html