Google LEMP River. I was referring to LAMP being the de-facto standard that is slowly being replaced by LEMP (linux, nginx, mysql, php), where you swap out Apache for NGINX (pronounced Engine-X), which is a much better webserver.
All those cool "cloud" content caching services you see these days use nginx as a reverse proxy. I use it purely as a webserver and unless you are doing all sorts of weird apache module crapola, NGINX drops right in and performs better.
If you need a second set of eyes to look at your apache stuff, let me know. Happy to look at a sanitised config and basic version stuff to recommend what I can. I'm not a web guru but I've run large scale apache installs in the past (/21 of addresses doing Vhosts for hundreds of sites), so might be of some help. I'm more a server and networking guy rather than a coding/application guy, and probably been using Linux as long as you River, despite our age gap.
a cronjob might be rather crude, but would work. I'd personally run some sort of monitoring or at least log tailing for certain signs that might warrant a HUP of the process.
Bookmarks