I’m working on my car to try and get some of the paint chips and pits out of the paint. Here are some pictures of the problem area’s.
I’ve been looking online at a couple of solutions.
www.popularmechanics.com/cars/how-to/repair/how-to-repair-chipped-car-paint
www.youtube.com/watch?v=dVkJT_hL6Zs&feature=related
The OtterBox Warranty Department asked that I provide them with pictures of the problematic OtterBox I purchased. Here they’re, as you can see the bottom iTunes Port cover has a small rubber line that is suppose to fit into the hard shell case, mine was defective upon receiving it. It worked fine for a while then just stopped working completely.
DomainPeople upgraded their Domain Name Manager, which now doesn’t allow the creation of Name Servers based on your domain name. So you’re required to submit a ticket to create/update your Name Servers based on your Domain Name. I’m so glad I moved to Hexonet, because I have direct access to this.
I’ve found the following configuration helps when you’re trying to squeeze out as much memory from a VPS as possible.
/private/var/mobile/Library/Preferences/XBMC/userdata/sources.xml
There is a bug in certain versions of Apache that is susceptible to a dDoS using malformed GET requests. You can find more information about “killapache” at the following site.
www.pentestit.com/2011/08/25/killapache-ddos-tool-freezes-apache-web-server/
There is no patch, however their is a work around for this bug which is provided below. In Ubuntu or Debian create a new file “/etc/apache2/conf.d/killapache-fix” and place the following code
You may need to install the “headers” module, which can be done by typing “a2enmod headers” and then you should be able to reload apache without errors.
When required to move large amounts data from one location to another, we use robocopy. Why? It’s basically like rsync for Linux, it copies NTFS Security ACL’s and will do file compare on every file to ensure that the destination has the most current version of the file.
So when moving over 50 + user folders, it comes in handy. We simply run robocopy a couple of days before to do the large sync of data. Then we run it during a maintenance window to update any files that have been modified or created.
It works great! But its biggest feature is that it will copy EFS files without the need to have the EFS certificate/key. Using the /EFSRAW switch allows for the copy of encrypted files from one location to another without having to decrypt the data.
Fore more information on the robocopy syntax please see the following site:
So I noticed that one of my servers wasn’t being backed up via email alerts recently. Usually I’m on top of it, but I noticed recently one less email from JungleDisk (I get completion notices on all JungleDisk Backups).
So I opened up the Jungle Disk Server Edition Management and found that I couldn’t connect to the machine I was trying to open. I thought, hrmm this happened before I just need to restart the “junglediskserver” process on the server in question. At which point I could then see the server listed in the Management console.
Once selected the server to see when the last backup was, I noticed it was 24 days from the last complete backup. I was super surprised and kinda ticked off because I didn’t notice this quick enough to fix it and neither did JungleDisk. I mean if there are 24 missed backup windows, don’t you think I should be notified.
I described the above to JungleDisk in an email to their Feedback address, lets see how they respond.
Update #1: I got a response from JungleDisk via email, they directed me to their Support System at which point I was able to post a feature request. But to my surprise their were already a handful of similar requests, so I dropped my two bits in. The one thread was over 2 years old. Great software, bad community relationship.
Update #2: I haven’t been following the thread on Jungledisk’s support site as I’ve pretty much decided to live with this problem. However, another awesome thing happened (I’m being sarcastic). Jungledisk was doing a backup and it either started super slow or during the backup it slowed down, either way the backup was going at 0.1k/s and wasn’t going to finish. It kept running, it missed the next backup window and I only knew this because I got no email about the job completing. You would think if a job takes too long and the next backup window is forthcoming, why not notify via email that it’s happening.
If you’ve used Google Page Speed then you’ve probably seen “Leverage browser caching” as one of the items on the Medium Priority list. And it’s a real simple fix if you’re running Apache. Just create or edit your .htaccess file for the site you want to enable it on and input the following.
And Viola, you’re now telling Web Browsers not to grab Images/CSS or Javascript unless otherwise required.
