Date: Tue, 5 Feb 2008 18:31:23 +0600 From: Victor Sudakov <sudakov@sibptus.tomsk.ru> To: remko@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/120288: zfs(1): "zfs share -a" does not send SIGHUP to mountd Message-ID: <20080205123122.GA24945@admin.sibptus.tomsk.ru> In-Reply-To: <200802051145.m15BjIhw041373@freefall.freebsd.org> References: <200802051145.m15BjIhw041373@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
remko@FreeBSD.org wrote: > Synopsis: zfs(1): "zfs share -a" does not send SIGHUP to mountd > > State-Changed-From-To: open->closed > State-Changed-By: remko > State-Changed-When: Tue Feb 5 11:45:18 UTC 2008 > State-Changed-Why: > Imo this is intended behaviour, no where in the manual is stated that > this should be possible etc. However, "zfs unshare -a" does reconfigure mountd! If this is intended behaviour, then be at least consistent (either you always reconfigure mountd, or you never do it). > Also when you add new shares in NFS you > should also restart mountd/sighup it, Not in Solaris at least. A person used to Solaris will be unpleasantly surprised by ZFS behaviour in FreeBSD. > so that the new shares become > visible, why should this be handled differently? Because a) one of the purposes of ZFS is easy management and b) "zfs unshare -a" *is* handled automatically. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080205123122.GA24945>