| Summary: | the peruser mpm is missing from the dev-lang/php | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Csaba Tóth <tsabi-gentoo> |
| Component: | New packages | Assignee: | Apache Team - Bugzilla Reports <apache-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | trivial | CC: | php-bugs |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Csaba Tóth
2006-08-27 09:36:11 UTC
Don't see what you mean, sorry. And, peruser is NOT safe w/ USE=threads. You need to explain your problem better. You right! Me sorry :) But than the apache why allow me to compile and install the peruser mpm with threading enabled? I think it should be warn me, or better dont allow me like the php does! :) (i dont remember i was warned or noticed.) The threads USE-flag is only used when you don't specify a mpm USE-flag. It does not check to see whether an mpm is thread safe or not. The threads USE-flag is only there to choose a default MPM if you don't specify one for yourself. USE=threads can be considered to be the same as USE=mpm-worker for the apache ebuild. @vericgar - this in NOTABUG from PHP point of view. If there's nothing to do on your side, please close accordingly. Than im confused now. I believe that the "threads" use flag means something at compile for the apache, because if it is disabled (but an mpm selected with use flag), and i try to install php with threading enabled, than it asks me to compile apache with threading enabled. But u r right, my original problem is not a real bug. Hmm, if it doesnt matter there is the "threads" use flag or not at the apache Ebuild, than why the PHP Ebuild look at that flag and asks me to turn it on or off? The logic in the PHP Ebuild, or the configure flags in the apache ebuild should be wrong. So i reopened this bug. Uhh no this is all correct ?!? The PHP ebuild works like this: if its "threads" USE flag is on, it checks that Apache2 was compiled with one of its threaded MPMs: mpm-event, mpm-worker, mpm-threadpool, etc. if the "threads" USE flag is off, it checks that Apache2 was compiled with one of its non-threaded MPMs: mpm-itk, mpm-peruser, mpm-prefork This is correct. Also the "logic" of the dev-lang/php "threads" USE flag has nothing to do with how the "threads" and "mpm-*" USE flags behave in Apache2, those are two different packages. Best regards, CHTEKK. You right. Ahh, lol, sorry guys, today was not my day :S |