Janno Sannik wrote: > Jille Timmermans wrote: >> Hello, >> >> I was attempting to run this patch in a FreeBSD jail (very lightweight >> virtual machine). >> The first problem was that this patches peruser.c, and I don't have that >> (yeah, well, had, but I rm -rf'ed my apache-dir, to apply this patch to >> a clean checkout). >> So, I looked at http://www.telana.com/peruser.php, but the patch >> downloadable there was with the same name as the attachment, and from 4 >> oct 2007. >> Is there some 'full version' somewere ? >> >> (I was intending to start FreeBSD-bughunting myself) >> >> Btw, I haven't found the meaning of those 'Multiplexers', what are they ? >> > The patch on telana page needs to be applied first. This creates the > peruser.c file. The patch submitted now patches the peruser.c and > mpm_default.h files. Use that order and you'll be fine. > The attatched patch is named httpd-2.2.3-peruser-0.3.0-dc1.patch and > telana peruser patch is named httpd-2.2.3-peruser-0.3.0.patch so names > does not match (but are similar for obvious reasons). I noticed the slight difference a few minutes after sending the email. > It's a good idea to keep patches oriented to last major version, so they > can be added, removed, investigated more easily. > > Multiplexers are owned by nobody and they get the connection, and pass > it to a proper child (processor/worker) which handles the request and > does the actual job. Ah, thanks
Next problem: I can't apply the (-dc1) patch: http://junk.quis.cx/ZxAczPHX/apache.typescript.txt Isn't there some CVS/SVN/GIT system where more people can easily checkout the latest version, and people can be assigned for committing ? I think it will enlarge the 'community' around peruser. And why does peruser still hang with apache 2.2.3 ? Changes in the minor don't (doesn't ?) sound like enormous changes that would break the entire peruser-mpm ? -- Jille _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
