On 9/4/2012 12:46 AM, Bryan Drewery wrote:
> On 9/4/2012 12:42 AM, Bryan Drewery wrote:
>> I am unable to get these to pass into jails via /etc/rc.d/jail + ezjail.
>>
>> I set them in the host:
>>
>> security.jail.mount_allowed=1
>> security.jail.mount_zfs_allowed=1
>>
>> What is the proper way to
On 9/4/2012 12:42 AM, Bryan Drewery wrote:
> I am unable to get these to pass into jails via /etc/rc.d/jail + ezjail.
>
> I set them in the host:
>
> security.jail.mount_allowed=1
> security.jail.mount_zfs_allowed=1
>
> What is the proper way to get these set?
>
>
I used `jail -m` to set thes
I am unable to get these to pass into jails via /etc/rc.d/jail + ezjail.
I set them in the host:
security.jail.mount_allowed=1
security.jail.mount_zfs_allowed=1
What is the proper way to get these set?
Bryan
___
freebsd-jail@freebsd.org mailing list
On 08/31/12 14:41, Scott Lambert wrote:
On Thu, Aug 30, 2012 at 07:05:30PM -0400, Darek M wrote:
On Thu, Aug 30, 2012 at 5:32 PM, John Nielsen wrote:
Another way to set hard quotas for jails is to give each one its
own filesystem of fixed size. This is trivially easy with zfs--just
create a z
On Sat, 25 Aug 2012, Jamie Gritton wrote:
...
Curtis
Offhand, it does sound like a bug. I imagine the solution would be to
reject the join - at least the easy solution to be done first until
something more complicated can be done to make jails play nice with
multicast.
- Jamie
Jamie,
Cert
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
