| #include<stdio.h> | |
| #include<string.h> | |
| #include<stdlib.h> | |
| #include<sys/mman.h> | |
| typedef void V;typedef int I;typedef double F;typedef unsigned char C,*S;typedef long L; | |
| #define O printf | |
| #define R return | |
| #define I(a...) if(a) | |
| #define W(a...) while(a) |
| ; -*-Emacs-Lisp-*- | |
| ; | |
| ; .bashrc | |
| ; # no ncurces glitches | |
| ; [[ $- == *i* ]] && stty sane | |
| ; export TERM=linux | |
| ; | |
| ; C-x RET r - revert buffer with coding system | |
| ; | |
| ; M-x occur - show minibuffer with searched results |
Mildly interesting results from string analysis of a handful of k files. If you have more public k files or suggestions for further analysis, comment below!
This uses the latest Shakti.
Corpus:
| 59 | |
| 73 41 | |
| 52 40 09 | |
| 26 53 06 34 | |
| 10 51 87 86 81 | |
| 61 95 66 57 25 68 | |
| 90 81 80 38 92 67 73 | |
| 30 28 51 76 81 18 75 44 | |
| 84 14 95 87 62 81 17 78 58 | |
| 21 46 71 58 02 79 62 39 31 09 |
| 75 | |
| 95 64 | |
| 17 47 82 | |
| 18 35 87 10 | |
| 20 04 82 47 65 | |
| 19 01 23 75 03 34 | |
| 88 02 77 73 07 63 67 | |
| 99 65 04 28 06 16 70 92 | |
| 41 41 26 56 83 40 80 70 33 | |
| 41 48 72 33 47 32 37 16 94 29 |
| > curl 'http://172.20.11.177:50070/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus' | |
| { | |
| "beans" : [ { | |
| "name" : "Hadoop:service=NameNode,name=NameNodeStatus", | |
| "modelerType" : "org.apache.hadoop.hdfs.server.namenode.NameNode", | |
| "State" : "active", | |
| "NNRole" : "NameNode", | |
| "HostAndPort" : "localhost:19000", | |
| "SecurityEnabled" : false, | |
| "LastHATransitionTime" : 0 |
| rm -f out | |
| mkfifo out | |
| trap "rm -f out" EXIT | |
| while true | |
| do | |
| cat out | nc -l 1500 > >( # parse the netcat output, to build the answer redirected to the pipe "out". | |
| export REQUEST= | |
| while read line | |
| do | |
| line=$(echo "$line" | tr -d '[\r\n]') |
From: https://beta.psy-dreamer.com/category/automation/deploying-from-github-to-vps-using-travis-ci
Recently, I spent around 14 to 16 hours learning all of the necessary steps to getting an existing repo set up with Travis CI to run unit tests, and then once successful, connect to a remote server that isn't a PaaS (in this case, Linode) and then proceeds to use Git hooks to do post deployment things.
Starting with your local machine and you have your project already checked out from Github.
gem install travis. This installs the Travis CI command-line tools. We're going to use these tools to encrypt RSA keys that Travis will use to connect to your remote server.