Zach Shepherd's WordPress Blog

It recently came to my attention that many people are unaware that apache will display the contents of a backup php file (e.g. “my1337password.php~”or “my1337password.php.bak”). This is because it doesn’t associate these files with the php parser. This can be easily prevented with a simple addition to the httpd.conf.

Example:
<Files ~ "\.(php|inc|config|cfg)(\~|\.bak|\.backup|\#)$">
Order allow,deny
Deny from all
Satisfy All
</Files>


Because Jeremy was kind enough to put together a 64-bit blade build, I was able to get all production blades (formerly 0001-0011, now hydrogen-lithium) running 64-bit installations, allowing for 64-bit domUs, which should increase overall performance (yay!).

Because backups are always nice, I also backed up the initial installation as a tar file (with setup instructions in the tar in /root/scrips/afterclone.txt). The backup is on raidA in the appropriately named location.

Someone mentioned I should probably make a post about the progress I made last workday, so I suppose I will.

• Lithium imaged with Berylium (and a script to back up (for dom0s) and instructions what to change after restoring the backup)
• Production Services to Lithium (except mirror and cosi)
• COSI image resized
• Old Nagios image renamed and New (64 bit) image creates
• Modification of Animal’s scripts to allow cluster to just be on the external network
• Updates to the wiki (updated creation instructions, added resize & rename instructions, updated running status on the images that changed dom0)
• Taking steps to quantify the I/O issues on animal (ran some basic tests, will be running iozone in the next few days)
• Fixing an issue involving things not being able to access /dev/null on etch-based images