id summary reporter owner description type status milestone component version severity resolution keywords cc 4694 Jailed FreeBSD needs BOOST_INTERPROCESS_FILESYSTEM_BASED_POSIX_SHARED_MEMORY Jim Bell Ion Gaztañaga "Note that one of the FreeBSD test platforms is failing many interprocess tests (both trunk and release), while the other passes. The one failing is in a [http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Jailed] environment (the other one isn't), and all failures seem to involve ""access denied"" (EPERM). Jails deliberately impose [http://www.freebsd.org/doc/en_US.ISO8859-1/books/arch-handbook/jail-restrictions.html some restrictions on shared memory]. If I modify BOOST_INTERPROCESS_FILESYSTEM_BASED_POSIX_SHARED_MEMORY (defined in interprocess/detail/workaround.hpp, lines 102) to be defined under __FreeBSD__ <= 8, I'm able to change a test from failing to passing. I'm not sure there's a way to tell if we're in a jail during compile. And even if we could, there would be a binary compatibility issue moving an executable built in a non-jailed environment to a jailed one. Is there a benefit to having this flag set one way or the other?" Bugs closed To Be Determined interprocess Boost 1.44.0 Problem fixed FreeBSD jail