On FreeBSD we can't access the shared memory after it was marked for deletion, unless this behaviour is explicitly enabled by the user. This behaviour can be enabled with the kern.ipc.shm_allow_removed sysctl variable which is set to 0 by default. In case it's not enabled we disable shm support.
On FreeBSD we can't access the shared memory after it was marked for
deletion, unless this behaviour is explicitly enabled by the user.
This behaviour can be enabled with the kern.ipc.shm_allow_removed
sysctl variable which is set to 0 by default.
In case it's not enabled we disable shm support.

This is not an issue on OpenBSD because we are allowing this by default
to follow what Linux does because most people will expect that.

BUG=
TEST=


Review URL: http://codereview.chromium.org/8910016

git-svn-id: de016e52bd170d2d4f2344f9bf92d50478b649e0@116959 0039d316-1c4b-4281-b951-d872f2087c98

adobe/chromium,adobe/chromium,gavinp/chromium,yitian134/chromium,adobe/chromium,gavinp/chromium,ropik/chromium,gavinp/chromium,yitian134/chromium,gavinp/chromium,adobe/chromium,yitian134/chromium,ropik/chromium,ropik/chromium,yitian134/chromium,adobe/chromium,gavinp/chromium,gavinp/chromium,gavinp/chromium,adobe/chromium,yitian134/chromium,adobe/chromium,ropik/chromium,gavinp/chromium,ropik/chromium,yitian134/chromium,adobe/chromium,adobe/chromium,ropik/chromium,ropik/chromium,adobe/chromium,gavinp/chromium,ropik/chromium,adobe/chromium,yitian134/chromium,yitian134/chromium,yitian134/chromium,yitian134/chromium,gavinp/chromium,ropik/chromium