Your docs belong in the code repository
Your docs is not extracted from code
Your docs features examples
You document every API call you provide
Your docs is easily accessible and browsed
Your docs should be easy to contribute to
That way in a moment of full-disk crisis I can simply delete it and buy myself some critical time to debug and fix the problem. 8GB is a significant amount of space, but storage is cheap enough these days that hoarding that much space is basically unnoticeable... until I really need it.
My solution to deal with this is to bind an IPv6 localhost ::1 socket to a given port. Only one process can do this, and thus it’s a very effective mutex. No lock files to cause havoc, no dealing with the dark and buggy corners of advisory file locking.
For shell scripts, simply replace the #!/bin/sh with #!/somewhere/bin/lock 2048 where 2048 is the port number you will use to enforce the lock (greater than 1024 if you do not want to deal with the hassles of privileged ports).
Trouvé sur le net:
« Quand vous prenez un TGV et que vous voulez utiliser le wifi
=> ouvrez la page de connexion
=> Demander l'aide du bot
=> Dites que vous avez un billet étranger
=> Voila, vous avez accès sans donner votre idenfication. Vous pouvez lancer votre vpn »