Date: Sun, 06 Jul 2014 10:35:04 +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-Co8EZxqOGo@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 --- Comment #7 from dreamcat4@gmail.com --- Created attachment 144450 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=144450&action=edit More comprehensive test cases & results OK. This occur on qjail 3.4. I have tested more thoroughly now. For full details of those testing (to know too what else is eliminated), is documented in the attached .TXT file "testing-details.txt". My new findings: * The problem only appears when jail is started by the 'qjail.bootime' rc.d script. * The problem does not occur if the jail is started from the command line (by typing "qjail start $jailname"). * The 'qjail.bootime' rc.script can be restarted once, twice, tree times. After bootup (of which not matter if occur with rest of system boot). And the reported problem (sysvipc not working) will still occur. Does not 'go away' 2nd time. Recommend: future investigations should focus more on what is happening inside the 'qjail.bootime' rc.d scipt. I will continue to look further. Many thanks. -- 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-Co8EZxqOGo>