2016-12-13 16:29, Alan Somers wrote:
I've already added support for sysvmsg, sysvsem, and sysvshm to
iocage. They all default to "new", which means you won't have to do
anything special in your jail config to make postgres work. You can
find the patch below. The only reason it hasn't been
I've already added support for sysvmsg, sysvsem, and sysvshm to
iocage. They all default to "new", which means you won't have to do
anything special in your jail config to make postgres work. You can
find the patch below. The only reason it hasn't been merged is
because it can't (yet) be made
2016-12-12 20:38, Christian Schwarz wrote:
With the new jail parameters, new namespaces for SysV IPC are possible
on FreeBSD 11.
For those ezjail users, add something like this to the jail's config
after creating it using 'ezjail-admin create':
export jail_postgres_parameters="sysvmsg=new
With the new jail parameters, new namespaces for SysV IPC are possible
on FreeBSD 11.
For those ezjail users, add something like this to the jail's config
after creating it using 'ezjail-admin create':
export jail_postgres_parameters="sysvmsg=new sysvsem=new sysvshm=new"
Cheers,
Christian
Regarding installation of PostgreSQL in a FreeBSD jail, the web hold
plenty of
warnings/advice that each postgres instance should have a unique UID,
otherwise
they stumble across each other's feet:
| allow.sysvipc
| A process within the jail has access to System V IPC primitives. In
the
|
