|
Graham Dumpleton
graham.dumpleton at gmail.com
Thu Jul 19 18:20:40 EDT 2007
You can also use: PythonOption mod_python.mutex_locks 4 at global scope in Apache configuration, ie., outside of VirtualHost containers, to limit how many session mutex locks that mod_python creates in the first place. There is also a 'configure' option to override the value when compiling mod_python itself. Your system does though look like it was creating too few so good idea to increase the system limit anyway as reducing it too much in mod_python may cause issues if you rely on mod_python sessions heavily. Graham On 19/07/07, andras at nic-nac-project.de <andras at nic-nac-project.de> wrote: > hi all, > when i try to run mod_python on NetBSD-3.1 using the generic kernel my apache error-log says: > > -- > [emerg] (28)No space left on device: Couldn't create accept lock (/var/run/accept.lock.16040) (5) > -- > > of course there is enough space left on the device and all the permissions are correct. > > > i was only able to fix this by changing the kernel config: > > GENERIC: > -- > #options SEMMNI=10 # number of semaphore identifiers > #options SEMMNS=60 # number of semaphores in system > #options SEMUME=10 # max number of undo entries per process > #options SEMMNU=30 # number of undo structures in system > -- > > MODIFIED CONFIG: > -- > options SEMMNI=32 # number of semaphore identifiers > options SEMMNS=60 # number of semaphores in system > options SEMUME=10 # max number of undo entries per process > options SEMMNU=30 # number of undo structures in system > -- > > > this is valid for the ports on i386 and also on amd64. > NetBSD does not permit to change SEMMNI via sysctl. > > > my current setup: > NetBSD-3.1 amd64 (or i386) > > apache-2.2.4nb6 > python24-2.4.4 > ap22-py24-python-3.2.10 > > > i hope this might be helpful to others. > > > regards, > andras > _______________________________________________ > Mod_python mailing list > Mod_python at modpython.org > http://mailman.modpython.org/mailman/listinfo/mod_python >
|