> Perhaps a more rational solution would be to have a "gateway" machine that
> keeps track of the number of httpd processes on each machine, then
> redirects the incoming connection request to an appropriate machine,
> instead of trying to run a bazillion processes on one machine. Hardware
> is cheap, especially older P166/P133/486dx4-100 hardware, and you could
> probably afford to put up several P133's for the price of a P300.
> Ed Carp, N7EKG erc@stripped 940/367-2744 cell phone
> Owner: WeatherAlert/Digital Weatherman - NWS alerts via email/pager/Internet
> DSOUTH-L backup, Terrorism, Shamanism, Hurricane mailing lists
Of course this is an option, as well. The tip about not running more than
30-40 processes is very useful, though. The specific issue about gateways
and bouncing specific tasks from one machine to another is somewhat
complicated due to the starkly different software environments running the
various businesses at this provider (IIS on NT vs. MySQL/Apache/PHP on
so, I think our approach will be to see how the first two "stores" run on
the Linux box, and, if the activity is excessive, there's always the K6.2
400 w/ 128M DIMMS I can throw at the problem if need be.
Thanks a lot for yours and everyone's feedback. This is an awesome group.