Hi SteveD, On Tue, Apr 16, 2019 at 10:34:51AM -0400, Steve Dickson wrote: > The only way I see a failure is when ./configure --with-pluginpath= > without a path which is wrong... > > ./configure --with-pluginpath=/usr/lib/libnfsidmap seems to work > just fine > > I thinking it is better to error out when a path is not given > then to gloss over but used a default. > > steved. > >From what you comments, there should be a plugin path assigned by default if the user is not aware of it, correct? Surely "./configure --with-pluginpath=/usr/lib/libnfsidmap" can work. But I didn't know the specific exact path before. I was just using "./configure" without any options and find out that it's empty. (Please find my previous full logs) Agree with you we should "use a default" one when path is not given. Thanks, Yongcheng
