I have already made the change in code for future release. Just to be safe, checking for both.
Thanks for the conformation is does fix the issue. On 06/05/2014, at 9:08 PM, George Barbăroşie <[email protected]> wrote: > Thanks all for the replies. Yes, I fixed the issue "by hand" on my system, I > just wanted to draw attention to the issue so that a fix can make it into the > project. > > On Sunday, 13 April 2014 04:12:28 UTC+3, Graham Dumpleton wrote: > Since you are compiling from source code, all you need to do is change > MPM_ITK to ITK_MPM in mod_wsgi.c file before running make. There is no other > change to be made for this issue. > > I am not sure when the next release of mod_wsgi will be. I am going to be > trying hard to get a new release out, but I am not sure what may get in the > way. > > Graham > > On 12/04/2014, at 9:09 PM, Chris Shelton <[email protected]> wrote: > >> I believe that I also ran into this exact issue on my gentoo system as well. >> I recently switched from prefork to the ITK MPM, and recompiled mod_wsgi >> and apache earlier today to attempt to switch my trac installation (using >> mod_wsgi) to a different virtual host host running as a different user id >> from the overall server default. >> >> After restarting apache, the socket file is still owned by the main apache >> user. I added a hack to chown the socket to the end of the start section of >> the init.d script, but it would be preferable for this to work without that >> customization. >> >> Is there a bug ID or ETA for when the fix to mod_wsgi will be available? >> Thanks for your work on this module. >> >> chris >> >> On Wednesday, April 9, 2014 6:50:34 AM UTC-4, Graham Dumpleton wrote: >> >> On 08/04/2014, at 5:04 AM, George Barbăroşie <[email protected]> wrote: >> >> > Hello, >> > >> > I'm confused at the use of #if defined(MPM_ITK) in mod_wsgi.c in >> > wsgi_setup_socket. On gentoo the apache headers compiled with mpm_itk >> > define ITK_MPM but not MPM_ITK and I cannot find anything in the mpm_itk >> > sources defining MPM_ITK. Version 2.2.17-01 of mpm_itk (the one for apache >> > 2.2 series) defines ITK_MPM as well as MPM_NAME "ITK", but it does not set >> > MPM_ITK at all. This seems to also be in line with other MPM's, i.e. >> > prefork defines PREFORK_MPM not MPM_PREFORK, worker defines WORKER_MPM, >> > etc. >> > >> > Could this be a typo in mod_wsgi or am I not looking in the right place in >> > the mpm_itk header files? >> >> Possibly. I went back to the original email about it from 2010 and it >> clearly had the correct way in it. >> >> What I don't understand is that people have used it successfully since then >> and no one else had said anything. >> >> Maybe it defined both at some point and removed the one which didn't match >> convention for other modules at some point. >> >> I could point at mod_fcgid and say they did it the same way, but actually >> looks like they copied what mod_wsgi was doing. :-) >> >> I will change it to check for both just in case. >> >> Graham >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "modwsgi" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/modwsgi. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/modwsgi. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
