2009/11/19 baloo <[email protected]>: > I solved this problem which was not jail specific at all. > You simply have to add this to the kernel config and recompile it: > options P1003_1B_SEMAPHORES > > Perhaps it should be possible to mension this in the error message > when trying to load?
Not possible as that original error message is likely generated by something outside of both Apache and mod_wsgi. BTW, be aware that support for Apache 1.3 after mod_wsgi 3.0 will start to disappear. You really should consider using Apache 2.2. Also, version 3.0 of mod_wsgi, provided you are using Apache 2.X, will have an ability to chroot individual mod_wsgi daemon mode process groups into different chroot environments, a possibly much more flexible system than having to chroot the whole of Apache. Graham > On Nov 18, 1:16 pm, baloo <[email protected]> wrote: >> I'm trying to load mod_wsgi 2.6 in apache 1.3 running in a FreeBSD 7.2 >> jail. >> >> httpd fails starting up with the message "Bad systemcall". >> >> ktrace shows that the call was: >> 1941 httpd CALL ksem_init(0x7fffffffe910,0x1) >> 1941 httpd RET ksem_init -1 errno 78 Function not implemented >> >> Disabling the mod_wsgi makes apache load again. >> I've also tried enabling security.jail.sysvipc_allowed using sysctl >> without luck. >> >> Any solution to this? > > -- > > You received this message because you are subscribed to the Google Groups > "modwsgi" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=. > > > -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
