On 04/23/2010 01:28 PM, Chuck Lever wrote: > On 04/23/2010 12:29 PM, Steve Dickson wrote: >> On 04/20/2010 04:46 AM, Mike Frysinger wrote: >>> The new code using libcap is quite minor, so rather than always reqiure >>> libcap support, make it a normal --enable type flag. Current default >>> behavior is retained -- if libcap is found, it is enabled, else it is >>> disabled like every nfs-utils version in the past. >>> >>> Signed-off-by: Mike Frysinger<vapier@xxxxxxxxxx> >>> >> Committed... > > I somehow missed this one. Why are we disabling libcap? And why are we > adding another --enable flag when everyone has agreed that we should > avoid that if at all possible? The justification I was used was it made nfs-utils more portable on systems/distros that may not have the libcap support. > > It is especially on older systems that nfs-utils will break without > libcap support. Without CAP_NET_BIND, pmap_unregister() will fail when > statd is shut down, leaving NSM registered with the portmapper, but with > no active listeners. When statd is started up again, it won't be able > to register the new NSM listener ports. Hmm... I agree the unregister() would fail on exit, but that's the reason an unregister() (and then an register) is done on start up before the privileges are drop... Actually this how it worked for a very long time, well before the capabilities support added... steved. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
