heroku config:add TZ="America/Denver"
.IPA - application/octet-stream
.PLIST - text/plain. |
| From Macgasm |
I then took it all apart again. Next, I removed the fan, snipped the #1 (see the arrows in the pic.) Then I soldiered in two 100 ohm resisters in parallel. The leads on each resistor are twisted with the duplicate lead on the other resistor putting them in parallel. The two ends of the #1 wire then were stripped and each end was soldiered to each side of the twisted resistors.
Next, with a Sharpie I also marked exactly where the fan was located on top of the aluminum plate. I drilled a pilot hole, then a 1 1/2" diameter hole to get the max amount to air into the unit.
Finally, in putting it all back together, I rotated the fan 90 degrees so that the output of the fan was pointing at the electronic boards (not the hard drive.) I used electrical tape to ensure the most of the air goes through the electronics and not out the sides (See pic).
Thanks to my neighbor who works for Axis cameras for loaning me the best IR camera I've ever seen: the Axis Q1910.This is just a quick post to save a much-queried DOS Batch file. This will delete hard returns from a given input file. Note that it does an append (">>") to the output file, so you will need to delete the output file each time you run this command.
Works like a champ!
I had a question from a customer yesterday on how to shutdown a non-responsive application. Of course, the best way to do it is to close it the normal way, but what do you do if nothing happens?
In Windows 7/8, I recommend these steps:
killtask /PID 1532This command will try to gracefully shutdown the process. This probably won't work if just clicking "close" in the application doesn't work. However, its a good thing to try first.
killtask /F /PID 1532
At this point one way or the other, that application is not running. If it still shows up when you type taskview, then there is a dependency problem with something else running. A reboot is in order.
A customer and I were reviewing their web logs and remarking on how many hits were coming in from countries with which they don't even remotely do business. There were several visits each day from China, Russia, Korea, etc. If they were coming to the site, they were either seriously lost or just up to no good.
We decided to restrict access to those folks that just shouldn't be there. Here is how we did it:
First, we are using IIS7. If you are using a Unix flavor, you need to modify your .htaccess file in the /etc directory. If you are on IIS, there is a similar procedure. You will be modifying the following file:
%WinDir%\System32\Inetsrv\Config\applicationHost.config
Open this file on your IIS Server and search for
location path=until you find the web instance you want to apply these settings to.
Next you want to get this file: http://ip-to-country.webhosting.info/downloads/ip-to-country.csv.zip This file is a list of IP addresses by country code.
The last thing to download is this excellent javascript file built by Kanwaljeet Singla. It parses the ip-to-country file into commands you can use in the applicationHost.config file. Once you have the file, rename it to: ipres.js
When you have everything, put it into a folder and pop open your command prompt and go to that directory. Here are a few interesting commands that Kanwaljeet built in:
// Generate an "allow" list for USA IP addresses cscript.exe //nologo ipres.js /f ip-to-country.csv /a USA
// Generate an "deny" list for China IP addresses cscript.exe //nologo ipres.js /f ip-to-country.csv /d China
So, here is how I got the website to deny anything but United States IP addresses:
cscript.exe //nologo ipres.js /f ip-to-country.csv /a USA > usa.txt
This created a file called usa.txt
<ipSecurity allowUnlisted="false">and the last "add" entry
<add ipAddress="10.0.0.0" subnetMask="255.0.0.0" allowed="true" />