Greg Ames <[EMAIL PROTECTED]> writes: > 2.0.34 built cleanly on daedalus. But when I tried to start it, I got: > > [gregames@daedalus apache2.0.34]$ tail logs/www/error_log > [Mon Apr 01 08:36:31 2002] [notice] suEXEC mechanism enabled (wrapper: > /usr/local/apache2.0.34/bin/suexec) > [Mon Apr 01 08:36:31 2002] [crit] (28)No space left on device: mod_rewrite: > could not create rewrite_log_lock > Configuration Failed > > The msg appears to be bogus; we have space. Here's the code:
ENOSPC is one of the possible errnos returned by SysV semaphore operations. You could do a truss and see which syscall is actually returning ENOSPC. I think JimJag changed the APR rules for picking the default mutex recently. That could have resulted in this change in behavior. If it were me I'd take two asynch approaches: 1) see what syscall failed and how to make it stop failing (OS tuning perhaps?) 2) validate that SysV sem is the proper mutex mechanism we should be using by default on FreeBSD -- Jeff Trawick | [EMAIL PROTECTED] Born in Roswell... married an alien...
