OpenBSD and Session::SysVSemaphoreLocker do not play well together

[Mark Wagner <ma...@horvitznewspapers.net>]

I encountered the same problem as given in this message:

--cut here--

FROM: Mark Jewiss
DATE: 01/19/2000 01:29:27
SUBJECT:  Apache::Session::DBI problems
           
Hello,

I`m trying to run a simple script using Apache::Session for the first
time, and am having a few problems. Can`t see anything relating to this in
the documentation or the archives, so here goes...

Whenever I run a script, everything works until I try to create a new
session id, where I get the following error:

No space left on device at
/usr/local/libdata/perl5/site_perl/Apache/Session/SysVSemaphoreLocker.pm
line 46.

This happens whether I use DBIStore or FileStore. I thought that this was
just down to my scripts, so I`ve gone back to the example script included
in the distribution. I get the same error when trying to run this.

I`m sure this is a simple issue, but I just can`t see the solution - any
help would be greatly appreciated!

Setup is as follows:

OpenBSD 2.5
Apache 1.3.6
Latest version of mod_perl and Apache::Session

--cut here--

A solution to the problem wasn't posted on the list.

The cause seems to be Session::SysVSemaphoreLocker. The workaround
I ended up using was creating a new type of Apache::Session that
uses Session::PosixFileLocker instead of Session::SysVSemaphoreLocker.

Searching the web I found this bit in a mod_ssl changelog about
OpenBSD and System V semaphores:

Disabled SysV IPC semaphore based mutex variant for FreeBSD < 3.0 and
any OpenBSD and NetBSD platforms because of conflicts with their
non-POSIX conforming semctl(2) prototypes.

HTH.

-
markw@horvitznewspapers.net