DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7921>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7921 perchild: apr_proc_mutex_[un]lock failed... [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs@httpd.apache.org Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2002-07-02 19:59 ------- You are trying to use SYS V Semaphores for your locking, but that can't work with perchild. The docs are not clear about this, because I just found the problem earlier this week. Basically, for all of the other MPMs, we create the semaphore and then change the permissions on the semaphore so that the child processes can attach to it. That works for the other MPMs, because they have a sinlge uid/gid for all of the child processes. Perchild doesn't have that, it has multiple uid/gid combinations, so we would have to make the permissions very lax in order to allow all of the uid/gid's to bind to the semaphore. Rather than open the security that much, it is much better to just use a fcntl locking mechanism. This can be accomplished by adding: AcceptMutex fcntl to your config file. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]