The FerretCam
August 6th, 2008Gem has started a FerretCam. Who knew that Ferrets could be so captivating.
Gem has started a FerretCam. Who knew that Ferrets could be so captivating.
Dear Google,
When I unsubscribe from a google-groups mailing list please unsubscribe me immediately, not after some arbitrary time delay as I have already deleted the relevant filters and now my Inbox is filling up.
Thank you.
Today I discovered the Hyper Text Coffee Pot Control Protocol. There’s a proper RFC and everything, most useful.
A conversation between my Wife and I as we were lying in bed listening to California Love by 2Pac on her new iPod shuffle:
me: Is this TuPac?
her: Yes.
me: Isn’t he dead?
her: Yes, this is a recording.
Remember, top-posting because that’s where the cursor happened to be is like shitting in your pants because that’s where your arsehole happened to be.
A. Yes it does, perfectly and at the highest detail level.
This is easy right? Can’t you just restart the memcached server? Well yes, but you may cause errors in applications that are already connected to it. You can follow your memcached restart with an application restart, eg for a Ruby on Rails app:
# /etc/init.d/memcached restart && mongrel_rails cluster::restart
Of course if you have more than one application server you have to restart your app on every single one. This would work on an engineyard slice assuming you have the eycap gem installed:
$ cap production memcached:restart
$ cap production mongrel:restart
Restarting your application is not ideal however, you will lose anything cached in memory, cause delays to users trying to access your site, that sort of thing.
So what can be done? The answer is really simple. Assuming a memcached running on the local machine on the default port:
$ echo ”flush_all” | nc localhost 11211
Easy!
I saw these amusing wireless network names on my way into Manchester to meet Paul Robinson the other week. Not had a chance to post them until now.
My wireless network is less imaginatively named ‘foo’.