From owner-freebsd-current@freebsd.org Sat Sep 19 00:08:14 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 59C1F3F47A8 for ; Sat, 19 Sep 2020 00:08:14 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BtWHx3CRhz4L6T for ; Sat, 19 Sep 2020 00:08:13 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from [10.0.10.15] (unknown [10.0.10.15]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id 871C420CC1 for ; Fri, 18 Sep 2020 17:08:05 -0700 (MST) Subject: Re: Documentation regarding NFSv4 To: freebsd-current@freebsd.org References: <20200918185319.7o27ciyviwdyhr7v@mutt-hbsd> From: "Russell L. Carter" Message-ID: Date: Fri, 18 Sep 2020 17:08:05 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Firefox/68.0 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-0.10 X-Rspamd-Server: h2 X-Rspamd-Queue-Id: 4BtWHx3CRhz4L6T X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.28 / 15.00]; RCVD_TLS_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[pinyon.org:s=dkim]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.05)[-1.045]; ARC_NA(0.00)[]; NEURAL_SPAM_SHORT(0.24)[0.243]; DKIM_TRACE(0.00)[pinyon.org:+]; DMARC_NA(0.00)[pinyon.org]; NEURAL_HAM_MEDIUM(-0.98)[-0.975]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:209, ipnet:65.101.0.0/18, country:US]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2020 00:08:14 -0000 On 2020-09-18 16:28, Rick Macklem wrote: > Oh, and I forgot to mention name<->id# mapping. > If using AUTH_SYS (not kerberos), then you have the > choice of running "nfsuserd" or setting these two sysctls to 1. > vfs.nfs.enable_uidtostring=1 > vfs.nfsd.enable_stringtouid=1 > --> This makes the server just handle id#s (uid, gid) as numbers in > a string. (This is the default for Linux these days although it was > ' frowned upon in the early days.) > > Running nfsuserd maps uid, gid numbers to/from names using the > password and group databases. This must be used for Kerberos mounts. > > Without the above properly configured, you'll see lots of files owned > by "nobody" on the client mounts. Those sysctls are interesting. I wasn't aware of them and so I run nfsuserd. What do they do, practically speaking? My understanding, likely wrong, is that nfsuserd should allow different uid/gid server->client mappings, possibly different for different clients. However I still had to sync uid/gids across machines even though they are all running nfsuserd. Didn't disable nfsuserd because... system is working... DFWI. Anyway, naked FreeBSD-stable nfsv4 is rock solid in a clamped down arena with a variety of FreeBSD and Debian clients. Kudos. Thanks, Russell > rick > > ________________________________________ > From: Rick Macklem