For instance, with today’s large disks you can get extra safety by using N=3, which would allow you to lose 2 disks without losing your data. If you used 4 * 2TB disks with N=3, for instance, you’d get 8/3TB of usable space, and be able to survive the loss of 2 disks. Gives you some interesting tradeoffs to explore.

So to help other users, this is the configuration I’m using in Archlinux and the latest nginx (1.2.1):

#default server
server {
listen 80 default_server;
listen [::]:80 default_server ipv6only=on;

# server_name is not to be specified in the default server
[...]
}

# virtual host
server {
listen 80;
listen [::]:80;

server_name example.com;

[...]
}

[etc.]

If you do not specify the listen clauses in the vhosts, you will ALWAYS get the default host for IPv6. Well, first thing was to figure out that it’s actually IPv6 only. Try that in a hybrid network.

Anyways, thanks a lot. Works like a charm!

http://httpd.apache.org/docs/2.1/platform/windows.html#windrivemap

Basically, it’s the same thing as you have come up with, but it also provides the answer as to why it doesn’t work the way you’d expect it to work (by simply using mapped drive, for instance).

Cheers!

screen -p 0 -S minecraft -X eval ‘stuff “save-all”15′
rsync -a –delete-after /srv/mc/ /path/to/minecraft/files/

The screen command wouldn’t wait for minecraft to finish saving, so the script would execute rsync almost immediately after sending the save-all command, before minecraft has had time to save the worlds.

There is a mistake in the last snippet that got me a bit crazy. It should be:
svn switch --relocate http://newdomain.com/path/to/old/repo http://newdomain.com/path/to/new/repo /path/to/working/copy

Source