FD_SETSIZE- The Final Solution?

The first round of posts thoroughly confused me, so i've been ignoring the problem and simply killing Apache when it occurs. But it seems to have developed an uncanny awareness of when i've gone fishing or to sleep.

I do option 2 that you mentioned (rebuild apache with larger FD_SETSIZE), and it works fine for me. Option 1 will also reduce the number of crashes, but may leave some customers out in the cold.... I never found it necessary to stop & restart apache in the middle of the night.... I normally do it manually ever few weeks, and its worked well so far....

I've gone with option (3) temporarily, since i like fishing and sleeping entirely too much. I suppose i'll have to get around to rebuilding Apache and seeing about the Zend bug, eventually.

My followup question is, having never used the easyapache script and not knowing what to expect, is it actually easy? I mean do i need to tell it anything special in order to reproduce my default CPanel configuration?

I'm not at all fond of the idea of manually rebuilding Apache, in order to get back where i started, for one stoopit little configuration thing.

Like anything else, after you've done it enough times it gets easy . First time, you may want to make sure you have a few days to hang around, so when someone tells you GD, Freetypes or something else their using isnt installed anymore, you can re-run it, and get it back for them.

To raise the limits, you'll need to choose option 6 (advanced). There you will need to check off everything you want installed (it doens't save the settings from the last build, so you need to re-check everything each time you rebuild, such as GD, php 4.31, etc).