summaryrefslogtreecommitdiffstats
path: root/contrib/libc++/src/regex.cpp
diff options
context:
space:
mode:
authorjamie <jamie@FreeBSD.org>2016-04-30 04:02:32 +0000
committerjamie <jamie@FreeBSD.org>2016-04-30 04:02:32 +0000
commit75525160315904c83a57f7fde43bdf7d0aa40a42 (patch)
treeb702d80e5fbb4b719a105ae465cdf6329ed024a7 /contrib/libc++/src/regex.cpp
parent8f241805478ee6cea6271b7f9181a35941763fbe (diff)
downloadFreeBSD-src-75525160315904c83a57f7fde43bdf7d0aa40a42.zip
FreeBSD-src-75525160315904c83a57f7fde43bdf7d0aa40a42.tar.gz
MFC r298584:
Note the existence of module-specific jail paramters, starting with the linux.* parameters when linux emulation is loaded. MFC r298585: Encapsulate SYSV IPC objects in jails. Define per-module parameters sysvmsg, sysvsem, and sysvshm, with the following bahavior: inherit: allow full access to the IPC primitives. This is the same as the current setup with allow.sysvipc is on. Jails and the base system can see (and moduly) each other's objects, which is generally considered a bad thing (though may be useful in some circumstances). disable: all no access, same as the current setup with allow.sysvipc off. new: A jail may see use the IPC objects that it has created. It also gets its own IPC key namespace, so different jails may have their own objects using the same key value. The parent jail (or base system) can see the jail's IPC objects, but not its keys. PR: 48471
Diffstat (limited to 'contrib/libc++/src/regex.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud