I’ve been using Windows 7 on my laptop since the 6801 build was first leaked in December ’08. However I only recently noticed that there is NO built-in tool for properly editing file type associations anymore. This is quite an annoyance, as I like to be able to assign custom icons and actions to my file types, such as adding an “Edit with Dreamweaver” to html files or “Open with Photoshop” to images. Having never used Vista, and since most of my time is spent on Linux and Mac OS now, I never noticed this annoyance before… ah Microsoft… I was happy with Windows 7 until now and this had me seriously considering going back to my XP/Leo/Ubuntu triple-boot.
Anyway enough rambling. Fortunately for my Windows 7 install, Google has answers for everything. A few minutes of googling revealed this page, which links to a handy little open-source(!) utility called Types that provides all the functionality of the built-in tool from Windows XP/2003 and older.
Types: a remedy for Microsoft's silliness.
Thank goodness for Sourceforge. And to the folks in Redmond… What is the deal with REMOVING functionality from your products? OK, you can provide a simple interface, but don’t make that simple interface slower and confusing for old users with old habits… or at least provide a way to revert to the classic behaviour! Which reminds me of another useless invention, the “Network and Sharing Center”…. but that’s another story.
So now I’m back at work after a good week off. The big project of the summer is Vmware migration, and the new equipment has just started coming in. We will be consolidating 20 servers into 4 VM hosts.
The specs of the system:
4 * Dell PowerEdge R710 servers (2*Intel Xeon X5550, 48GB RAM)
Dell EqalLogic iSCSI SAN 16 x 450GB @15K RPM
We have received the four servers, but can’t start until the SAN arrives…
Rented a cottage up in Tobermory. Quite a nice experience, waking up to see the lake and nature. Also got a chance to relax and enjoy the quiet and take some nice photos. Visited Flowerpot Island and did some hiking on the Bruce trail.
I currently have WordPress running in an OpenVZ container behind a lighttpd reverse proxy. Because of this, the source IP for all comments was being detected as 172.16.32.201 (my lighttpd proxy). The solution was found on the WordPress support forum.
All I needed to do was add
if(isset($_SERVER['HTTP_X_FORWARDED_FOR'])) {
$list = explode(',',$_SERVER['HTTP_X_FORWARDED_FOR']);
$_SERVER['REMOTE_ADDR'] = $list[0];
}
to wp-config.php. This bit checks if HTTP_X_FORWARDED_FOR is set in the HTTP request, and if so, uses it for the REMOTE_ADDR.
Update:
I found a better way to do this, assuming that the backend server is running apache2. Just install mod_rpaf. On Debian:
apt-get install libapache2-mod-rpaf
Then edit /etc/apache2/mods-enabled/rpaf.conf and set your proxy IP. This also allows apache’s access.log to show the real client IP.
One minor bug (not sure if it’s because of this code or lighttpd or my network setup) is that all the proxied IPs are prefixed with ::ffff:. In any case it’s just a minor annoyance.
Quick note:
using LDAP’s default port 389 with a Base DN of the parent Active Directory domain only shows objects from the parent domain. Changing the port to 3268 but keeping the same Base DN allows LDAP access to users from the child AD domain.
So, finally got the Openfire Jabber server to see all users from both domains.
Found via: http://www.igniterealtime.org/community/message/155746
For further reading: http://technet.microsoft.com/en-ca/library/cc978012.aspx
Kind of a lame first post, but hey, gotta start somewhere!
Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!