Date: Sat, 05 Jul 2014 22:02:14 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-jail@FreeBSD.org Subject: [Bug 191279] [jail] jail allow.sysvipc - doesn't work until jail is started TWICE after reboot Message-ID: <bug-191279-9824-WclYv4KnAG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-191279-9824@https.bugs.freebsd.org/bugzilla/> References: <bug-191279-9824@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191279 zilly <freebsdbugs@zilly.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsdbugs@zilly.org --- Comment #4 from zilly <freebsdbugs@zilly.org> --- I have the identical issue using Freebsd 10.0, qjail 3.4, and the allow.sysvipc flag. It does not matter whether security.jail.sysvipc_allowed is set to 0 or 1 on the host. # uname -oprUK FreeBSD 10.0-RELEASE-p6 amd64 1000510 1000510 Relevant section of qjail log file on first jail start: FATAL: could not create shared memory segment: Function not implemented DETAIL: Failed system call was shmget(key=5432001, size=40, 03600). Like dreamcat4, sysvipc works once the jail has been started a second time after each time the host boots. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191279-9824-WclYv4KnAG>