Check These Out
Checks HDD for bad sectors, just like scandisk or chkdisk under some other operating system ;-).
With the "--resolve" switch, you can avoid doing DNS lookups or edit the /etc/hosts file, by providing the IP address for a domain directly. Useful if you have many servers with different IP addresses behind a load balancer. Of course, you would loop it:
$ for IP in 10.11.0.{1..10}; do curl --resolve subdomain.example.com:80:$IP subdomain.example.com -I -s; done
credit to tumblr engineering blog @ http://engineering.tumblr.com/
Useful to get network access to a machine behind shared IP NAT. Assumes you have an accessible jump host and physical console or drac/ilo/lom etc access to run the command.
Run the command on the host behind NAT then ssh connect to your jump host on port 2222. That connection to the jump host will be forwarded to the hidden machine.
Note: Some older versions of ssh do not acknowledge the bind address (0.0.0.0 in the example) and will only listen on the loopback address.
If you are blocked or need to use a Socks proxy
You might want to secure your AWS operations requiring to use a MFA token. But then to use API or tools, you need to pass credentials generated with a MFA token.
This commands asks you for the MFA code and retrieves these credentials using AWS Cli. To print the exports, you can use:
`awk '{ print "export AWS_ACCESS_KEY_ID=\"" $1 "\"\n" "export AWS_SECRET_ACCESS_KEY=\"" $2 "\"\n" "export AWS_SESSION_TOKEN=\"" $3 "\"" }'`
You must adapt the command line to include:
* $MFA_IDis ARN of the virtual MFA or serial number of the physical one
* TTL for the credentials
Say your dependencies specified in your Makefile (or dates on your source files) is causing 'make' to
skip some source-files (that it should not) or on the other other end, if it is causing make to always build some source-files regardless of dates of target, then above command is handy to find out what 'make' thinks of your date v/s target date-wise or what dependencies are in make's view-point.
The egrep part removes the extra noise, that you might want to avoid.
Listens for events in the directory. Each created file is displayed on stdout. Then each fileline is read by the loop and a command is run.
This can be used to force permissions in a directory, as an alternative for umask.
More details:
http://en.positon.org/post/A-solution-to-the-umask-problem%3A-inotify-to-force-permissions
swap out "80" for your port of interest. Can use port number or named ports e.g. "http"
