![]() |
| | >>> Click
here to download Final Fantasy Ringtones |
| Administrator |
#9 I'm mad as a |
| | |
| |
| Banned | In the famous words of Yams: I'll live thought nothing against you putting forth a forum problem ![]() And since we are on the topic of discussing forum problems, I, once again, want to protest against this forums childs labor ordiments. They should extend to the internet as well |
| | |
| | weird, never had the sig overflow issue ![]() I dont know anything about the server but I have seen issues like that when people use the apache 2.0 setup with linux Has to do with the fact that it's engeneered to run more on a threaded OS such as windows. This only happens on only larger high traffic servers though -- which i belive this is. There are a lot of hosts who erronously use Apache 2.0 on the *nix boxes. Don't ask why... they should be using 1.3Like I say i know this much about this site |---| but its just a suggestion as ususal..../shrug Bipper |
| | |
| Administrator | Just to get all the facts straight: (obligatory rant following) Apache 2.0 is a threading application (as opposed to 1.3, which forks) which does make it a prime candidate for Windows servers. The main problem can occur when concurrent threads try to access resources simultaneously, which can happen more frequently under heavy traffic. However, that does not exclude it from *nix systems at all as most of the problems are introduced by using non-thread-safe modules. (the apache 2.0 core is far more stable than the modules in this case) In fact, Apache 2.0 does have it's advantages over 1.3. We could use Apache 2.0 seamlessly on this server as long as it were configured correctly. The main reasons why many hosts (us included) still use 1.3: » Some modules such as mod_throttle or mod_bwlimited are still only for 1.3, and many web control panels such as Cpanel/WHM (which we use) rely on these modules to provide certain important features » If it ain't broke... » 2.0 and 1.3 perform similarly in general cases » Apache 1.3 is a forking application, and thus is still very suitable for *nix servers. (not to say 2.0 isn't suitable, forking is just safe and efficient under *nix) When Apache 2 modules become completely thread safe and the core application reaches maturity, it will desired over 1.3 for both Windows and *nix. However, it still can be used with Linux, given that it's configured correctly. Ok, all done. ![]() </rant> |
| | |