Fix Retina MacBook poor battery life

The first of these, is to clear the PRAM and NVRAM settings. This seems to be a favorite of Apple support staff, as I recall being told to try this on a couple of pre-MacBook era machines for various things. To do it is really simple:

• First, power off your MacBook Pro
• Then, when you power up, hold down the cmd+option+P+R keys all at the same time
• When you see it cycle round and you hear the startup sound again, let go and let your MacBook Pro boot up as normal.

This on its own may resolve the problem. The other method that runs in conjunction with this involves a little terminal:

• Open up Terminal on your MacBook Pro
• Type in cd ~/Library/Preferences/ then press enter
• Then type rm com.apple.desktop.plist and press enter
• Finally, type killall Dock and hit enter again

This command will delete the settings file listed in the second line, and restart your dock so you're not running with any faulty preferences anymore. It also seems to set your wallpaper back to the stock, Mountain Lion wallpaper, so that may be a good sign that you did everything right.

Source

http://www.imore.com/how-resolve-battery-life-troubles-your-retina-macbook-pro

Show hidden files in OSX Finder utility

You can use a Terminal command to reveal the hidden files in OS X by making a change to the default behavior of Finder.

defaults write com.apple.Finder AppleShowAllFiles TRUE
killall Finder

reference:

http://computers.tutsplus.com/tutorials/quick-tip-revealing-hidden-files-in-os-x--mac-48663

Manually setting date time on Linux (Raspberry Pi, Beagle Bone, ...)

sudo date -s "17 Aug 2014 13:14:30"

How to Assign the .local Domain to Your Raspberry Pi

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install avahi-daemon

source:

http://www.howtogeek.com/167190/how-and-why-to-assign-the-.local-domain-to-your-raspberry-pi/

Network resources exhausted - TCP/IP ports are in a TIME_WAIT status

Lately on old Windows 2008 R2 servers I had some network problems.
So I connected to the server via VNC or Remote Desktop and after hours spent without a clue, I tried a "netstat -n" command from DOS prompt and I got an infinite list of TCP/IP ports are in a TIME_WAIT status...

So, what is happening? It seems that there is a strange bug that sometimes Windows does not reuse socket ports in TIME_WAIT status, so when it reaches the maximum port number (65000 or so), the server cannot anymore create new sockets (beware that listening sockets are Ok, so You can connect to the server and all inbound connections actually work, only outbound are rejected).

At this point the only solution is the reboot of the server.

Microsoft has a bug fix but it needs reboot as well:
http://support.microsoft.com/kb/2553549/en-us

TCP/IP ports that are in a TIME_WAIT status 

TCP/IP ports that are in a TIME_WAIT status