Apache

Our site at $work is generating Apache logs that, when combined sequentially into one file, are larger than 50GB in size for one day's worth of traffic. AWStats' perl script pretty much chokes when working on this much data. Last I checked, Webalizer wasn't much different, and probably wouldn't scale up to that amount of data either. Does anyone out there have any advice on a commercial solution for Apache log analysis that can scale up like that?

At work, I've been working on an upgrade from a custom-compiled version of Apache 2.0.x to the Sun-provided Glassfish Webstack 1.5.  I spent about a week troubleshooting what I thought was configuration issue, only to finally find it's a bug way upstream in Apache 2.2.12+.  This bug only affects Solaris 10, and is near-impossible to reproduce.  If you use Solaris 10 and Apache, read on so you don't waste a week of your life like I did.

I've done a lot with LVM in the past, but up until now had never really played around with LVM snapshots. I recently used LVM snapshots to implement a "hot backup" of my LAMP stack running this blog. I quote "hot backup" because, while mysql is indeed running, I do have to place a read lock on all tables for a second or two. You don't need to do this if you're using Innodb, but you do if you use the MyISAM engine (which Drupal does by default).

Mozilla Weave is a project from Mozilla Labs that aims to keep all of your browser data synced between all of your PC's.  The now defunct Google Browser Sync used to do this, as does Foxmarks.  Although Weave is still in it's infancy, it's been very promising thus far.  However, many of the users of Mozilla's own Weave server complain that the service is very slow.  The beauty of Weave is that it uses the standard protocol WebDAV to sync it's data.  Why does that matter?  Because our good 'ol buddy Apache can speak WebDAV out-of-the box!  Follow the jump to find out how you can setup your own server that you can sync to.