I have to say, my server is performing beyond my initial expectations! I think I have everything tweaked to not use massive amounts of RAM (coughMySQLcough.) Here’s how the free -m currently looks: $ free -m total used free shared buffers cached Mem: 121 90 31 0 2 46 -/+ buffers/cache: 41 80 Swap: 1121 14 1107 As you can see, it’s doing pretty good. I’ve even upped the maximum simultaneous Apache connections since it seems to be able to handle that a better now (rather then bringing the server to its knees when something like 10-15 people tried to access it at once.

Well, I think I have all the previous issues taken care of. Caching may or may not work, but it’s supposed to be happening now. So mail and DNS lookups work now (DNS only being useful from my side.) So, all-in-all I hope this beast can just run for several months and I’ll see what (if anything) needs to be done in that time. So now that my server should be stable, I’m free to work on other endevors!

Well now that the system is live, I think there’s going to be a few things I’m going to need to fix. Most all of them are from using mod_chroot. Most aren’t anything critical, but things that should be addressed (sooner rather than later.) For instance, I think DNS lookups are failing from inside WordPress. I breifly read in the mod_chroot caveates that this may happen, and I think this is happening now.

 As I prepare to have my server public, I’ve chrooted my server’s Apache with mod_chroot. This allows me to have the advantages of a chroot environment without as many of the draw backs. There is still some strangeness to work out. For instance “Warning: timezone_open() [function.timezone-open]: Unknown or bad timezone (America/Chicago) in /wp/wp-includes/functions.phpon line 3160” I’ll get this figured out, but honestly, it’s not a huge deal. I may have to have Apache load the zoneinfo file, or perhaps not… Really, the only change I had to make to WordPress was to have it connect to the MySQL database on 127.