Date: Tue, 22 May 2012 09:20:05 GMT From: "Dewayne" <dewayne.geraghty@heuristicsystems.com.au> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/168191: sysutils/ezjail + freebsd9 -stable --> dont work Message-ID: <201205220920.q4M9K5tJ030092@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/168191; it has been noted by GNATS. From: "Dewayne" <dewayne.geraghty@heuristicsystems.com.au> To: <bug-followup@FreeBSD.org>, <jamie@FreeBSD.org> Cc: <superbofh@gmail.com> Subject: Re: ports/168191: sysutils/ezjail + freebsd9 -stable --> dont work Date: Tue, 22 May 2012 19:12:23 +1000 I'm able to experience a similar failure when starting a jail subsystem after a reboot. If you reverse the patch http://lists.freebsd.org/pipermail/svn-src-stable-9/2012-May/001815.html your jail functionality will return. That is: Cut/paste the patch from http://lists.freebsd.org/pipermail/svn-src-stable-9/2012-May/001815.html into say j.diff cd /usr/src/lib/libjail patch jail.c j.diff make; make install; /usr/local/etc/rc.d/ezjail start # or restart For the benefit of the developer (Jamie). I'm not technical so I couldn't debug the code, however: The error message after . /usr/local/etc/ezjail/b1 sh -x /etc/rc.d/jail onestart b1 was + tail +2 /tmp/jail.43t9sZRC/jail.5444 jail: unknown parameter: allow.nomount These parameters were included and passed to a modified ezjail export jail_b1_parameters="allow.sysvipc allow.raw_sockets" I've included these to demonstrate that I don't use, or pass the allow.nomount parameter, and hope that it provides you a useful clue. Regards, Dewayne.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201205220920.q4M9K5tJ030092>