Date: Fri, 21 Sep 2012 15:38:50 -0700 From: Tim Gustafson <tjg@soe.ucsc.edu> To: freebsd-fs@freebsd.org Subject: Re: Exporting ZFS File System to Multiple Subnets Message-ID: <CAG27QgT-Rr6B%2BBZ5LUs6%2B%2Bg_BEMoArKBxJW%2BdOYiJ7yCrenFFw@mail.gmail.com> In-Reply-To: <CAG27QgTYg-K553bnPffVC9FhCthCDqGWLVayBPv86NJeCAoE6Q@mail.gmail.com> References: <CAG27QgQbwot1%2Bfu=2PmQYpaqKqb8Ob8sieb28XuXJDaWbZnKqQ@mail.gmail.com> <20120922004036.88462@relay.ibs.dn.ua> <CAG27QgTYg-K553bnPffVC9FhCthCDqGWLVayBPv86NJeCAoE6Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> the only way to do that I know is described here: > http://freebsd.1045724.n5.nabble.com/zfs-sharenfs-to-multiple-subnets-found-a-dirty-looking-hack-td4030378.html > > I've seen that, but it certainly feels "dirty". Wouldn't it just be better to disable the "sharenfs" property altogether, or make it a non-operational property, and allow regular /etc/exports rules to work? Or perhaps have a psuedo-value for the "sharenfs" property that would enable normal /etc/exports processing? Something like: zfs set sharenfs=exports tank I'd rather edit /etc/exports by hand anyhow. -- Tim Gustafson tjg@soe.ucsc.edu 831-459-5354 Baskin Engineering, Room 313A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG27QgT-Rr6B%2BBZ5LUs6%2B%2Bg_BEMoArKBxJW%2BdOYiJ7yCrenFFw>