Titre:asher256's blog | devops/linux engineer in montreal, canada
La description :asher256's blog devops/linux engineer in montreal, canada search main menu skip to primary content skip to secondary content home contact puppet module to configure lizardfs (distributed file system)...
Classement Alexa Global: # 1,733,715
Server:Apache... X-Powered-By:PHP/5.6.37
L'adresse IP principale: 198.54.126.25,Votre serveur United States,Austin
ISP:Ross Technology Inc. TLD:com Code postal:us
Ce rapport est mis à jour en 31-Jul-2018
Created Date:
2009-08-28
Changed Date:
2017-03-20
Expires Date:
2019-08-28
Données techniques du asher256.com
Geo IP vous fournit comme la latitude, la longitude et l'ISP (Internet Service Provider) etc. informations.
Notre service GeoIP a trouvé l'hôte asher256.com.Actuellement, hébergé dans United States et son fournisseur de services est Ross Technology Inc. .
montreal times - montreal's english weekly newspaper
Analyse d'en-tête HTTP
Les informations d'en-tête HTTP font partie du protocole HTTP que le navigateur d'un utilisateur envoie à appelé Apache contenant les détails de ce que le navigateur veut et acceptera de nouveau du serveur Web.
IP:198.54.126.25 ASN:22612 OWNER:NAMECHEAP-NET - Namecheap, Inc., US Country:US
mx:
MX preference = 0, mail exchanger = mail.asher256.com.
HtmlToText
asher256's blog devops/linux engineer in montreal, canada search main menu skip to primary content skip to secondary content home contact puppet module to configure lizardfs (distributed file system) on linux posted on february 24, 2017 by asher256 1 i recently published the puppet module puppet-lizardfs (give the project a star on github to support the project!) you can use to configure lizardfs, a highly-available distributed file system (dfs). lizardfs makes files secure by keeping all data in many replicas spread over several linux servers. the puppet module puppet-lizardfs is an open source project, and community contributions are essential for keeping it great. i encourage you to contribute. send me your pull requests on github! currently, puppet-lizardfs supports the operating systems debian/ubuntu and redhat/centos. a puppet example: continue reading → posted in posts | 1 reply 3 advices to write robust bash scripts posted on may 25, 2016 by asher256 reply to write robust bash scripts, i recommend you to: 1. activate the bash options: errexit, nounset add these two options at the top of your bash scripts: #!/usr/bin/env bash set -o errexit set -o nounset 1 2 3 #!/usr/bin/env bash set - o errexit set - o nounset errexit will stop your bash script each time a command in your script returns an exit code different than “0”. it does not show any message when it quits, this is why it is important to show a traceback (check the second advice below “show a bash traceback”). nounset will stop your script and output an error if you attempt to use undefined variables. nounset is very important because it can avoid you to run dangerous commands like: rm – fr “/$undefinedvariable” 2. show a bash traceback because the option “errexit” does not show any message when it stops your bash script in some cases (for example var=$(yourcommand) will exit without any message, even when yourcommand returns an exit code different than zero), i recommend you to add the code below to show a traceback each time “errexit” forces your bash script to stop: #!/usr/bin/env bash set -o errexit # stop the script each time a command fails set -o nounset # stop if you attempt to use an undef variable function bash_traceback() { local lasterr="$?" set +o xtrace local code="-1" local bash_command=${bash_command} echo "error in ${bash_source[1]}:${bash_lineno[0]} ('$bash_command' exited with status $lasterr)" if [ ${#funcname[@]} -gt 2 ]; then # print out the stack trace described by $function_stack echo "traceback of ${bash_source[1]} (most recent call last):" for ((i=0; i < ${#funcname[@]} - 1; i++)); do local funcname="${funcname[$i]}" [ "$i" -eq "0" ] && funcname=$bash_command echo -e " $i: ${bash_source[$i+1]}:${bash_lineno[$i]}\t$funcname" done fi echo "exiting with status ${code}" exit "${code}" } # provide an error handler whenever a command exits nonzero trap 'bash_traceback' err # propagate err trap handler functions, expansions and subshells set -o errtrace 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 #!/usr/bin/env bash set - o errexit # stop the script each time a command fails set - o nounset # stop if you attempt to use an undef variable function bash_traceback ( ) { local lasterr = "$?" set + o xtrace local code = "-1" local bash_command = $ { bash_command } echo "error in ${bash_source[1]}:${bash_lineno[0]} ('$bash_command' exited with status $lasterr)" if [ $ { #funcname[@]} -gt 2 ]; then # print out the stack trace described by $function_stack echo "traceback of ${bash_source[1]} (most recent call last):" for ( ( i = 0 ; i < $ { #funcname[@]} - 1; i++)); do local funcname = "${funcname[$i]}" [ "$i" - eq "0" ] && funcname = $ bash_command echo - e " $i: ${bash_source[$i+1]}:${bash_lineno[$i]}\t$funcname" done fi echo "exiting with status ${code}" exit "${code}" } # provide an error handler whenever a command exits nonzero trap 'bash_traceback' err # propagate err trap handler functions, expansions and subshells set - o errtrace the traceback will help you to know exactly which command in your bash script exited with an error code different than “0”: error in ./test.sh:43 ('false' exited with status 1) traceback of ./test.sh (most recent call last): 0: ./test.sh:43 false 1: ./test.sh:49 main exiting with status -1 1 2 3 4 5 error in . / test . sh : 43 ( 'false' exited with status 1 ) traceback of . / test . sh ( most recent call last ) : 0 : . / test . sh : 43 false 1 : . / test . sh : 49 main exiting with status - 1 3. check your bash scripts with shellcheck and follow the recommendations of advanced bash-scripting guide . posted in posts | leave a reply temporarily prevent linux from shutting down posted on may 5, 2016 by asher256 reply accidental shutdown or reboot is a serious blunder, especially if the kernel is being updated in the background. in order to prevent linux from shutting down while your update script is running, i recommend you to use systemd-inhibit: systemd-inhibit --why="doing update" ./my-update-script.sh 1 systemd - inhibit -- why = "doing update" . / my - update - script . sh systemd-inhibit will block the shutdown or reboot until the update script is finished. additional options: –who=”your name” a human-readable name — list list all active inhibition locks posted in posts | leave a reply how to stop and remove all docker images and containers posted on may 3, 2016 by asher256 reply docker is a great tool, but sometimes it can consume a lot of disk space. docker-clean is a simple bash script you can use to remove all docker images and containers with one command: $ git clone https://github.com/zzrotdesign/docker-clean $ cd docker-clean $ ./docker-clean --help options: -h or --help opens this help menu -v or --version prints the current docker-clean version -a or --all stops and removes all containers, images, and restarts docker -c or --containers stops and removes stopped and running containers -i or --images stops and removes all containers and images -net or --networks removes all empty networks -s or --stop stops all running containers --dry-run adding this additional flag at the end will list items to be removed without running the remove or stop commands -l or --log adding this as an additional flag will list all image, volume, and container deleting output 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 $ git clone https : //github.com/zzrotdesign/docker-clean $ cd docker - clean $ . / docker - clean -- help options : - h or -- help opens this help menu - v or -- version prints the current docker - clean version - a or -- all stops and removes all containers , images , and restarts docker - c or -- containers stops and removes stopped and running containers - i or -- images stops and removes all containers and images - net or -- networks removes all empty networks - s or -- stop stops all running containers -- dry - run adding this additional flag at the end will list items to be removed without running the remove or stop commands - l or -- log adding this as an additional flag will list all image , volume , and container deleting output to stop and remove all docker containers: $ ./docker-clean --containers 1 $ . / docker - clean -- containers to remove all docker images: $ ./docker-clean --images 1 $ . / docker - clean -- images posted in posts | leave a reply about blog dedicated to linux, docker, ansible, ceph distributed storage and other devops topics. my nick name is asher256 and work as a devops/linux engineer in a large-scale, high-volume production environment, at gameloft (montreal city, canada). my github projects dockerfile-patch puppet-lizardfs puppet-redis_cluster python-cmdwrapper python-dirtree other github projects recent posts puppet module to configure lizardfs (distributed file system) on linux 3 advices to write robust bash scripts temporarily prevent linux from shutting down how to stop and remove all docker images and containers recent comments amara on pupp
Whois est un protocole qui permet d'accéder aux informations d'enregistrement.Vous pouvez atteindre quand le site Web a été enregistré, quand il va expirer, quelles sont les coordonnées du site avec les informations suivantes. En un mot, il comprend ces informations;
Domain Name: ASHER256.COM
Registrar URL: http://www.godaddy.com
Registrant Name: Registration Private
Registrant Organization: Domains By Proxy, LLC
Name Server: NS1.DREAMHOST.COM
Name Server: NS2.DREAMHOST.COM
Name Server: NS3.DREAMHOST.COM
DNSSEC: unsigned
For complete domain details go to:
http://who.godaddy.com/whoischeck.aspx?domain=ASHER256.COM
The data contained in GoDaddy.com, LLC's WhoIs database,
while believed by the company to be reliable, is provided "as is"
with no guarantee or warranties regarding its accuracy. This
information is provided for the sole purpose of assisting you
in obtaining information about domain name registration records.
Any use of this data for any other purpose is expressly forbidden without the prior written
permission of GoDaddy.com, LLC. By submitting an inquiry,
you agree to these terms of usage and limitations of warranty. In particular,
you agree not to use this data to allow, enable, or otherwise make possible,
dissemination or collection of this data, in part or in its entirety, for any
purpose, such as the transmission of unsolicited advertising and
and solicitations of any kind, including spam. You further agree
not to use this data to enable high volume, automated or robotic electronic
processes designed to collect or compile this data for any purpose,
including mining this data for your own personal or commercial purposes.
Please note: the registrant of the domain name is specified
in the "registrant" section. In most cases, GoDaddy.com, LLC
is not the registrant of domain names listed in this database.
REGISTRAR GODADDY.COM, LLC
REFERRER http://www.godaddy.com
SERVERS
SERVER com.whois-servers.net
ARGS domain =asher256.com
PORT 43
SERVER whois.godaddy.com
ARGS asher256.com
PORT 43
TYPE domain RegrInfo DOMAIN
NAME asher256.com
NSERVER
NS1.DREAMHOST.COM 64.90.62.230
NS2.DREAMHOST.COM 208.97.182.10
NS3.DREAMHOST.COM 66.33.205.230
STATUS clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited clientRenewProhibited https://icann.org/epp#clientRenewProhibited clientTransferProhibited https://icann.org/epp#clientTransferProhibited clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Nous utilisons des cookies pour personnaliser votre expérience sur notre site. En poursuivant votre navigation, vous acceptez cette utilisation. Apprendre encore plus
asher256.com rapport :
Visitez le site