From owner-freebsd-current@freebsd.org  Sun May 14 07:11:18 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id C5F14D6C600
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 14 May 2017 07:11:18 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 839DBE19
 for <freebsd-current@freebsd.org>; Sun, 14 May 2017 07:11:18 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1d9ngK-0005vU-Cu; Sun, 14 May 2017 10:11:08 +0300
Date: Sun, 14 May 2017 10:11:08 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject: Re: more default uid/gid for NFS in mountd
Message-ID: <20170514071108.GK1188@zxy.spb.ru>
References: <YTXPR01MB01895E8D60DD369C1762785DDDEE0@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
 <20170508134203.GA3165@zxy.spb.ru>
 <YTXPR01MB0189D5B7CADD42D195E9855BDDE00@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <YTXPR01MB0189D5B7CADD42D195E9855BDDE00@YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 May 2017 07:11:18 -0000

On Sun, May 14, 2017 at 01:12:11AM +0000, Rick Macklem wrote:

> >> It is also the case that mountd.c doesn't look "nobody" up in the password database
> >> to set the default. It would be nice to do this, but it could result in the mountd daemon
> >> getting "stuck" during a boot waiting for an unresponsive LDAP service or similar.
> >> Does doing this sound like a good idea?
> >
> >This is (stuck at boot) already do for case of using NIS and nfsuserd.
> There is a difference here. nfsuserd mpas between uid/names, so it can't work
> without the password database.
> mountd can work without the password database, so I held off on doing this for now.
> 
> >I am regular see this for case of DNS failed at boot.
> >You offer don't impair current behaviour.
> As an aside, if you have the critical entries in the local files (/etc/hosts, /etc/passwd,
> /etc/group) and then tell the libraries to search these first in /etc/nsswitch.conf, then
> you usually avoid this problem.

Same as for 'nobody' for mountd?

> Thanks for the comments, rick
> 

Thanks!