WordPress update monitoring

If you’re reading this, you know I rarely visit my blogs. That presents a problem, as I never get the nag from WordPress that my version is so out of date, my site has been taken over by Russian Yakuza using it to spy against the Chinese on behalf of Syria or something. Below is a simple little script that can be thrown in cron and will bug you when WordPress releases a new version and you’ve not updated.

DIRS="Insert list of directories with wordpress here"

for dir in $DIRS ; do
if [ -f $current_file ] ; then
current=`grep ^\\$wp_version $current_file | awk '{print $NF}' | sed s/\;//g | sed s/\'//g`
survey_says=`wget -O - -o /dev/null http://api.wordpress.org/core/version-check/1.0/?version=$current`
if [ $survey_says != "latest" ] ; then
echo "$dir Needs an upgrade!!!!"
echo "Currently $current"
echo "$current_file does not exist!"

The key here is the URL “http://api.wordpress.org/core/version-check/1.0/?version=”. Append a version number to the end of that, and it will tell you if you’re at the latest or need to upgrade.

How to configure Netatalk on Ubuntu to be TimeMachine Server

Seems Pretty Straight Forward:
sudo apt-get update
sudo apt-get install netatalk
sudo apt-get install avahi-daemon

/huge/TimeMachine "TimeMachine" options:tm to

Create /etc/avahi/services/afpd.service with contents:
<name replace-wildcards=”yes”>%h</name>

Restart everything:
sudo service netatalk restart && sudo service avahi-daemon restart

iPhone, iPad and PCs

So Read-it-later is a webs service that allows you to book mark articles to read later. The did an interesting analysis of what people read when and on what devices. Their results compare pretty much to my usage profile for the iPhone and iPad.

The iPad is a couch consumption device. I use it for reading email, quick email replies, reading facebook, surfing the web, and as an e-reader. I don’t find it good for creating content out side of the most basic snark-attacks on someone’s wall.

The iPhone for me, before it started sucking wind, was what the Read it Later people say it was – a downtime device. Something to due while waiting in line, stuck in traffic, or during a boring meeting.

When I want to do real content creation, I do it on my Mac. Nothing beats a full-sized keyboard, a 27″ monitor, multiple windows open, etc.

That is why I don’t expect Apple to do away with their MacOSX product line. iOS is great for consumption. OSX is great for creation. Sure some guy claims he edited a movie on his iPad. That means it can be done, not that that is the way it should be done.

January 28th, 1986

“Ask ten different scientists about the environment, population control, genetics, and you’ll get ten different answers, but there’s one thing every scientist on the planet agrees on. Whether it happens in a hundred years or a thousand years or a million years, eventually our Sun will grow cold and go out. When that happens, it won’t just take us. It’ll take Marilyn Monroe, and Lao-Tzu, and Einstein, and Buddy Holly, and Aristophanes…[and] all of this…all of this…was for nothing. Unless we go to the stars”. – Commander Jeffrey Sinclair, Babylon 5

Reasons why the English language is so hard to learn:

1) The bandage was wound around the wound.
2) The farm was used to produce produce.
3) The dump was so full that it had to refuse more refuse.
4) We must polish the Polish furniture.
5) He could lead if he would get the lead out.
6) The soldier decided to desert his dessert in the desert.
7) Since there is no time like the present, he thought it was time to present the present.
8 A bass was painted on the head of the bass drum.
9) When shot at, the dove dove into the bushes.
10) I did not object to the object.
11) The insurance was invalid for the invalid.
12) There was a row among the oarsmen about how to row.
13) They were too close to the door to close it.
14) The buck does funny things when the does are present.
15) A seamstress and a sewer fell down into a sewer line.
16) To help with planting, the farmer taught his sow to sow.
17) The wind was too strong to wind the sail
18) After a number of injections my jaw got number.
19) Upon seeing the tear in the painting I shed a tear.
20) I had to subject the subject to a series of tests.
21) How can I intimate this to my most intimate friend?
22] I want it to be on record that I wll record my record.

DoubleCloud » What Lessons You Can Learn from Google on Building Infrastructure

I’m going to add this site to my blogroll. The author is one of VMWare’s R&D honchos.

Interesting tid-bit on how to DOS Google if you’re so inclined.

Some of the search queries can cause huge IO. One example Jeff gave is “circle of life” as one phase enclosed in double quotation marks. It could incur 30GB I/O before. As I just searched on Google, the phrase is now a song name. I bet it’s now in Google’s cache server.

When there are so many servers to manage, something unique happened. Jeff mentioned an interesting phenomenon called “query of death.” If a query can causes a server to crash, then it can crash all other servers because the software stack is the same. To avoid large scale of crashes, they used canary request which is first sent to one machine. If it’s good, then send it to the rest of machines; otherwise reject the request after failing several times. It of course adds a little delay but far better than large scale system crash. Of course, you need to log down the query and found out why it crashed software as a process of continuous improvement. Jeff didn’t mention this, but I bet Google did that.

via DoubleCloud » What Lessons You Can Learn from Google on Building Infrastructure.

So, I wonder what the I/O load is on google if I did a search on:

“Ubuntu Private Cloud Prince William Engagement” or “MySQL Replication Senator McConnell Earmark ban”
Pick any two other totally different subject and combine them into a single query.