From owner-freebsd-virtualization@freebsd.org Sun Apr 29 16:11:11 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4ED12FB0DFD for ; Sun, 29 Apr 2018 16:11:11 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from mail.io7m.com (mail.io7m.com [IPv6:2001:19f0:5:752:f000::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.io7m.com", Issuer "arc7 CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F1AC875307 for ; Sun, 29 Apr 2018 16:11:10 +0000 (UTC) (envelope-from list+org.freebsd.virtualization@io7m.com) Received: from almond.int.arc7.info (unknown [IPv6:2a02:390:7502:2:0:2:4:0]) by mail.io7m.com (Postfix) with ESMTPSA id 9D3723750; Sun, 29 Apr 2018 16:11:09 +0000 (UTC) Date: Sun, 29 Apr 2018 17:10:57 +0100 From: Mark Raynsford To: freebsd-virtualization Cc: "Rodney W. Grimes" Subject: Re: Read-only view of a ZFS filesystem inside a bhyve guest? Message-ID: <20180429171057.6fe9bf8c@almond.int.arc7.info> In-Reply-To: <20180428113635.4b6b567a@almond.int.arc7.info> References: <20180427174341.03373bc8@almond.int.arc7.info> <201804271842.w3RIgIIo007831@pdx.rh.CN85.dnsmgr.net> <20180428113635.4b6b567a@almond.int.arc7.info> Organization: io7m.com OpenPGP: id=B84E17747616C6174C68D5E55C1A7B712812CC05; url=http://io7m.com/pgp/B84E_1774_7616_C617_4C68_D5E5_5C1A_7B71_2812_CC05.key MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/2DL2Y_mqB8Y6vLpNuaxbBWh"; protocol="application/pgp-signature" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 16:11:11 -0000 --Sig_/2DL2Y_mqB8Y6vLpNuaxbBWh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On 2018-04-28T11:36:35 +0100 Mark Raynsford via freebsd-virtualization wrote: > > Well that's two in favour of NFS. I have one small question: Is there > any way to stop nfsd from forking into the background? I run everything > on the system under process supervision (runit), and this is the first > time I've ever seen a daemon program with no option to stay in the > foreground. >=20 > I can write a wrapper in C that starts up rpcbind and nfsd (the former > *does* have an option to stay in the foreground), but I'd rather not if > I don't have to. I spent a while writing a wrapper[0] that keeps nfsd in the foreground and cleans up when it shuts down, only to discover that there's an entirely undocumented --debug flag[1] that does the same thing. [0] https://github.com/io7m/nfswrap-bsd [1] https://github.com/freebsd/freebsd/blame/master/usr.sbin/nfsd/nfsd.c#L1= 05 --=20 Mark Raynsford | http://www.io7m.com --Sig_/2DL2Y_mqB8Y6vLpNuaxbBWh Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQS4Thd0dhbGF0xo1eVcGntxKBLMBQUCWuXukQAKCRBcGntxKBLM Bc8/AQDxz9PQ3MR3xFGsh7zSHmqdwHznTYOOyoT4+Cc2MYGC7gEAzStS9YTKWXry J1vvjE3szetIyf1dBz5X26mN4NekBQQ= =N85n -----END PGP SIGNATURE----- --Sig_/2DL2Y_mqB8Y6vLpNuaxbBWh--