Re: HEADS UP: Win32/OS2/BeOS native ports

On Sun, 5 May 2002, Joel Burton wrote:

> > "Joel Burton" <joel(at)joelburton(dot)com> writes:
> > >> Rather than propagating the SysV semaphore API still further, why don't
> > >> we kill it now? (I'm willing to keep the shmem API, however.)
> >
> > > Would this have the benefit of allow PostgreSQL to work properly in BSD
> > > jails, since lack of really working SysV IPC was the problem there?
> >
> > Was the problem just with semas, or was shmem an issue too?
>
> Not sure -- doesn't get far enough for me to tell. initdb dies with:
>
> creating template1 database in /usr/local/pgsql/data/base/1...
> IpcSemaphoreCreate: semget(key=1, num=17, 03600) failed:
> Function not implemented

Read the jail manpage:

jail.sysvipc_allowed
This MIB entry determines whether or not processes within a jail
have access to System V IPC primitives. In the current jail imple-
mentation, System V primitives share a single namespace across the
host and jail environments, meaning that processes within a jail
would be able to communicate with (and potentially interfere with)
processes outside of the jail, and in other jails. As such, this
functionality is disabled by default, but can be enabled by setting
this MIB entry to 1.