nfs-utils.git/utils/nfsd, branch gss-fixes

nfsd: fix minorversion-choosing interface

2014-01-07T20:57:48+00:00

From: "J. Bruce Fields" 

By unconditionally adding ?4.2 to the version string written to the
kernel we make nfs-utils incompatible with pre-4.2-supporting kernels.

Ditto for 4.1.  This problem was introduced by
12a590f8d556c00a9502eeebaa763d906222d521 "rpc.nfsd: Allow v4.2 server
support with the -V option", which also change nfsd to unconditionally
pass ?4.2.

Instead, just don't mention 4.1 or 4.2 unless the commandline has
specifically requested that one or the other be turned on or off.

Tested-by: Joakim Tjernlund 
Reported-by: Joakim Tjernlund 
Signed-off-by: J. Bruce Fields 
Signed-off-by: Steve Dickson

rpc.nfsd: Allow v4.2 server support with the -V option

2013-08-19T17:04:50+00:00

Signed-off-by: Steve Dickson

rpc.nfsd: No longer advertise NFS v2 support.

2013-08-19T17:04:49+00:00

Changed the default protocol versions that rpc.nfsd
register with rpcbind to just 3 and 4. Version 2
can still be enabled with the '-V' flag, but it
will not be on by default.

Signed-off-by: Steve Dickson

nfsd: Add support for the -V and --nfs-version optional arguments

2013-03-25T20:07:59+00:00

Add command line options to enable those NFS versions that are
currently disabled by default. We choose to use the options '-V'
and '--nfs-version' for compatibility with rpc.mountd.

Acked-by: J. Bruce Fields 
Signed-off-by: Trond Myklebust 
Signed-off-by: Steve Dickson

nfsd: Bump up the default to 8 nprocs

2012-03-16T15:00:15+00:00

When the nproc argument is not given the rpc.nfsd
a default number of processes is created. This
patch bumps that default up from 1 to 8.

Signed-off-by: Steve Dickson

autoconf: only link binaries that need it to libtirpc

2012-01-16T19:40:21+00:00

This patch is essentially the same as the previous version, but has
been respun to fix up some merge conflicts with some of Chuck's
recent changes.

When we first added tirpc support, we took a "big hammer" approach, and
had it add libtirpc to $LIBS. That had the effect of making it so that
that library was linked into every binary. That's unnecessary, and
wasteful with memory.

Don't let AC_CHECK_LIB add -ltirpc to $LIBS. Instead, have the autoconf
tests set $(LIBTIRPC) in the makefiles, and have the programs that
need it explicitly include that library. In the event that we're not
using libtirpc, then set $LIBTIRPC to a blank string.

This necessitates a change to the bindresvport_sa check too. Since that
library is no longer included in $LIBS, we need to convert that check
to use AC_CHECK_LIB instead of AC_CHECK_FUNCS.

This patch also fixes a subtle bug. If the library was usable, but the
includes were not, the test would set $enable_tirpc to "no", but
HAVE_LIBTIRPC would still be true. That configuration would likely
fail to build.

Signed-off-by: Jeff Layton 
Signed-off-by: Steve Dickson

man pages: fixed a few typos in a couple man pages

2011-10-04T16:47:27+00:00

Signed-off-by: Steve Dickson

nfsd: allow choosing server 41 support at runtime

2011-09-20T11:41:36+00:00

In the case where -N 4.1 is left off the commandline, the current code
explicitly turns it on or off anyway, depending on configure options.

Instead, just leave 4.1 support alone.  This allows a user to add an
"echo +4.1 >/proc/fs/nfsd/versions" to their init scripts, if they want.
Otherwise they will get the kernel's default (currently to leave 4.1
off, as long as 4.1 support is experimental).

Signed-off-by: J. Bruce Fields 
Signed-off-by: Steve Dickson

pdate addres for Free Software Foundation

2011-08-29T16:57:07+00:00

License texts contain multiple address for FSF, some wrong.
So update them and  replace COPYING file with
http://www.gnu.org/licenses/gpl-2.0.txt
which has a few changes to preamble and commentary.

Also remove extra COPYING file from utils/statd/

Signed-off-by: NeilBrown 
Signed-off-by: Steve Dickson

supress socket error when address family is not supported

2011-05-23T12:25:11+00:00

From: Suresh Jayaraman 

It was observed that when ipv6 module was not loaded and cannot be auto-loaded,
when starting NFS server, the following error occurs:
	"rpc.nfsd: unable to create inet6 TCP socket: errno 97 (Address
	family not supported by protocol)"

This is obviously a true message, but does not represent an "error" when ipv6
is not enabled.  Rather, it is an expected condition.  As such, it can be
confusing / misleading / distracting to display it in this scenario.

This patch instead of throwing error when a socket call fails with
EAFNOSUPPORT, makes it as a NOTICE.

Signed-off-by: Suresh Jayaraman 
Signed-off-by: Neil Brown 
Signed-off-by: Steve Dickson