Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jun 2014 16:57:11 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 191279] New: jail allow.sysvipc - doesn't work until jail is started TWICE after reboot
Message-ID:  <bug-191279-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191279

            Bug ID: 191279
           Summary: jail allow.sysvipc - doesn't work until jail is
                    started TWICE after reboot
           Product: Base System
           Version: 9.2-RELEASE
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: dreamcat4@gmail.com

This is one of the most weird bug I have come across since using FreeBSD ja=
ils.

I have now made an rc.d script to restart my jail a 2nd time every boot=E2=
=80=A6 and
sysvipc feature will then start working inside of the jail.

Without such intervention, a jail is normally started 1 time after system
reboot. Then for me it isn't working inside of the jail.

This concerns only "allow.sysvipc" in jail.conf file. I have not set any ot=
her
kinds of "global" sysvipc options for the host or the jail.

Sorry I can't provide a test case for this problem. It was found with
qjail-3.4, on FreeNAS. But it would be great if anyone else can try to
reproduce this situation. To see if it occurs on any other FreeBSD versions=
 -
9.2, 9.3, 10.0, STABLE or CURRENT.


My uname -a:

FreeBSD freenas.local 9.2-RELEASE-p3 FreeBSD 9.2-RELEASE-p3 #0 r262572+7b72=
365:
Fri Mar 14 15:50:04 PDT 2014=20=20=20=20
root@build.ixsystems.com:/home/jkh/9.2.1-BRANCH/freenas/os-base/amd64/tank/=
home/jkh/9.2.1-BRANCH/freenas/FreeBSD/src/sys/FREENAS.amd64
 amd64

--=20
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-8>