Date: Mon, 12 Dec 2016 20:38:17 +0100 From: Christian Schwarz <me@cschwarz.com> To: Mark Martinec <Mark.Martinec+freebsd@ijs.si> Cc: freebsd-stable@freebsd.org Subject: Re: Is System V IPC namespace still shared across jails? Message-ID: <20161212193817.hjax5jo5leb7ryjr@csarch.Speedport_W_724V_01011603_00_008> In-Reply-To: <bd0104e960902c42acef95555c0fc37f@ijs.si> References: <bd0104e960902c42acef95555c0fc37f@ijs.si>
next in thread | previous in thread | raw e-mail | index | archive | help
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 --- man 8 jail > ... > > allow.sysvipc > A process within the jail has access to System V IPC > primitives. This is deprecated in favor of the per- > module parameters (see below). When this parameter is > set, it is equivalent to setting sysvmsg, sysvsem, and > sysvshm all to ``inherit''. > > ... > > sysvmsg > Allow access to SYSV IPC message primitives. If set to > ``inherit'', all IPC objects on the system are visible to this > jail, whether they were created by the jail itself, the base > system, or other jails. If set to ``new'', the jail will have > its own key namespace, and can only see the objects that it has > created; the system (or parent jail) has access to the jail's > objects, but not to its keys. If set to ``disable'', the jail > cannot perform any sysvmsg-related system calls. > > sysvsem, sysvshm > Allow access to SYSV IPC semaphore and shared memory primitives, > in the same manner as sysvmsg. > > ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161212193817.hjax5jo5leb7ryjr>