Comment 7 for bug 883155

I've pushed an alternate solution to the problem using flock() instead of shared memory segments to remove the possibility of leaking resources. It creates the new lock file (per Perl process) which resides in the configured pid dir. Note, this patch makes a necessary change to opensrf-perl.pl (which is easy to miss if your manually patching your system instead of installing from the branch).

http://git.evergreen-ils.org/?p=working/OpenSRF.git;a=shortlog;h=refs/heads/collab/berick/perl-server-read-write-flock

Needs testing in an environment that suffered from the original issue...