W.Kenworthy wrote:
> Hi, I am looking the current apache upgrade to -r31. There are a number
> of MPM ("Multi-Processing Module implementing a hybrid multi-threaded
> multi-process web server") related use flags. I have not seen any
> discussions on these so is there anyone willing to comment on their
> "desirability" - is this something that most apache servers (in my case
> low load, static html) would benefit from/be harmed by?
>
> Also, have there been any glitches with the apache -r31 major changes,
> or has that gone off problem free, or is everyone being like me and
> still waiting and for the first person to jump just in case!
>
> BillK
> There is documentation on the MPMs in the upgrading guide [1]. In summary though, you will probably prefork or worker. prefork is the same style that apache-1.3 uses, which forks a new process for each child (children can handle a certain number of requests). worker is a hybrid forking and threading MPM, it forks several processes, which each thread. It has better performance, but any module you use will have to be thread-safe. Note that you don't have to specify a mpm-* USE-flag - if none of them are set, sane defaults are used. As far as upgrading, if you follow the docs [1], it should be problem free - however if you've changed your default config it may take you some time to get it working the same in new-style as old-style. If you do have issues, there are several knowledgeable devs in #gentoo-apache on irc.freenode.net that are more then happy to help. [1] http://www.gentoo.org/doc/en/apache-upgrading.xml -- Michael Stewart [EMAIL PROTECTED] Gentoo Developer http://dev.gentoo.org/~vericgar GnuPG Key ID 0x08614788 available on http://pgp.mit.edu --
signature.asc
Description: OpenPGP digital signature
