Date: Sun, 06 Jul 2014 01:36:19 +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-suCGgEzLct@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 joeb1@a1poweruser.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joeb1@a1poweruser.com --- Comment #5 from joeb1@a1poweruser.com --- When you say the allow.sysvipc parameter has no effect on a jails first start after system boot. Just how are you determining this? Do you see the "allow.sysvipc" listed by the "jls -name -j jailname" command. I installed 10.0 from disc1.iso to a empty hard drive and running qjail-3.4 and after starting the jail "jls -name -j jailname" shows "allow.sysvipc" which means its enabled, and no error messages in the jails console log. Seeing jls showing the "allow.sysvipc" instead of "allow.nosysvipc" is the only indicator I have available to verify its being set correctly. This indicator does not really prove the sysvipc function for the jail is functional. As far as I know you need to run some application in the jail that requires sysvipc access as the only true test. This application may have to be started one time to set some application internal default setting before it knows sysvipc is enabled on its second start. Look for a application configure file to set sysvipc as the default instead of the tcp default setting. What application are you running in the jail and how does that application get started? Almost 99% sure your problem is caused by your jailed application and not qjail or jail(8). -- 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-suCGgEzLct>