From owner-freebsd-bugs@FreeBSD.ORG Tue Feb 5 13:31:28 2008 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36AD816A417; Tue, 5 Feb 2008 13:31:28 +0000 (UTC) (envelope-from sudakov@sibptus.tomsk.ru) Received: from relay2.tomsk.ru (relay2.tomsk.ru [212.73.124.8]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD1313C448; Tue, 5 Feb 2008 13:31:26 +0000 (UTC) (envelope-from sudakov@sibptus.tomsk.ru) X-Virus-Scanned: by clamd daemon 0.91.2 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakovva@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.13) with ESMTPSA id 9576668; Tue, 05 Feb 2008 18:31:23 +0600 Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.13.6/8.13.6/Submit) id m15CVNxc025066; Tue, 5 Feb 2008 18:31:23 +0600 (OMST) (envelope-from sudakov@sibptus.tomsk.ru) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to sudakov@sibptus.tomsk.ru using -f Date: Tue, 5 Feb 2008 18:31:23 +0600 From: Victor Sudakov To: remko@FreeBSD.org Message-ID: <20080205123122.GA24945@admin.sibptus.tomsk.ru> References: <200802051145.m15BjIhw041373@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200802051145.m15BjIhw041373@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://vas.tomsk.ru/vas.asc Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/120288: zfs(1): "zfs share -a" does not send SIGHUP to mountd X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2008 13:31:28 -0000 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