Très intéressant l'algo utilisé par nginx pour choisir le bloc server et ensuite le bloc location. Je me demande si il existe des astuces pour debug en cas de problèmes... (comment savoir dans quel(s) bloc(s) passe une request ?)
-
https://www.digitalocean.com/community/tutorials/understanding-nginx-server-and-location-block-selection-algorithms
-
http://www.agilemobiledeveloper.com/2015/06/10/why-12-factor-application-patterns-microservices-and-cloudfoundry-matter-part-2-what-to-change-and-how/They all sux to visualize difference EXCEPT:
1) murphy
2) torte
:colorscheme murphy
-
https://links.infomee.fr/?3de1_g.ssh/authorized_keys
environment="GIT_AUTHOR_NAME=Arnaud M",environment="GIT_AUTHOR_EMAIL=arnaud@foo.bar",environment="GIT_COMMITTER_NAME=Arnaud M",environment="GIT_COMMITTER_EMAIL=arnaud@foo.bar" ssh-rsa .....
Peut être pratique quand plusieurs personnes commit depuis le même serveur (pour avoir un historique git avec les noms..)
-
http://cweiske.de/tagebuch/carry-git-settings.htmcontexte : le plugin firefox que j'utilise pour checker nagios ne permet pas de filtrer comme je veux les alertes c'est à dire :
https://nagiosserver/nagios/cgi-bin/status.cgi?host=all&servicestatustypes=28&serviceprops=41002&hostprops=41002&sorttype=1&sortoption=6&sorttype=1&sortoption=1
Solution temporaire, crado, de la rewrite avec nginx :
server {
listen 80 default_server;
location / {
rewrite ^.*$ /nagios/cgi-bin/status.cgi?host=all&servicestatustypes=28&serviceprops=41002&hostprops=41002&sorttype=1&sortoption=6&sorttype=1&sortoption=1 break;
proxy_pass https://nagiosserver;
proxy_redirect off;
}
}
Je fais tourner ça en local, je fais pointer mon plugin sur localhost, et voilà !
-
https://links.infomee.fr/?2MGbUwmysql -N -e 'show databases' | while read dbname; do mysqldump --complete-insert --routines --triggers --single-transaction "$dbname" > "$dbname".sql; done
todo : regarder les options
-
https://ma.ttias.be/mysql-back-up-take-a-mysqldump-with-each-database-in-its-own-sql-file/Probleme de conversation cachée...
To solve this "LoggedOut" issue, try this on any chat window:
/msnp24
and restart your Skype.
After restarting, /dumpmsnp output shows the following status:
System: MSNP: Connection Data (MSNP24):
-
https://community.skype.com/t5/Linux/Skype-group-chat-not-working-anymore/td-p/3987288TIL :
-
https://links.infomee.fr/?FJATHQUn output compact au high state
-
https://gist.github.com/JustinCarmony/e1f764bc650999ac872eSometimes it may happen that your vm has hanged and XenCenter controls(Reboot and Force Reboot) do not work.
You may see an error when you try to force a reboot (The operation could not be performed because a domain still exists for the specified VM.).
This is a process to reboot the hanged vm from the XenServer host console.
To get the uuid of the VM that is hung:
xe vm-list
Get the vm domain id by uuid:
list_domains
Then destroy the domain of the vm:
/opt/xensource/debug/destroy_domain -domid <domid>
Now you can force a reboot on your vm:
xe vm-reboot uuid=<uuid> --force
If it has no effect you can also try:
xe vm-reset-powerstate uuid=<uuid> --force
-
http://www.xenlens.com/restart-a-hanged-virtual-machine/