| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and server. This replaces the RPC implementation of the NFS client and
server with the newer RPC implementation originally developed
(actually ported from the userland sunrpc code) to support the NFS
Lock Manager. I have tested this code extensively and I believe it is
stable and that performance is at least equal to the legacy RPC
implementation.
The NFS code currently contains support for both the new RPC
implementation and the older legacy implementation inherited from the
original NFS codebase. The default is to use the new implementation -
add the NFS_LEGACYRPC option to fall back to the old code. When I
merge this support back to RELENG_7, I will probably change this so
that users have to 'opt in' to get the new code.
To use RPCSEC_GSS on either client or server, you must build a kernel
which includes the KGSSAPI option and the crypto device. On the
userland side, you must build at least a new libc, mountd, mount_nfs
and gssd. You must install new versions of /etc/rc.d/gssd and
/etc/rc.d/nfsd and add 'gssd_enable=YES' to /etc/rc.conf.
As long as gssd is running, you should be able to mount an NFS
filesystem from a server that requires RPCSEC_GSS authentication. The
mount itself can happen without any kerberos credentials but all
access to the filesystem will be denied unless the accessing user has
a valid ticket file in the standard place (/tmp/krb5cc_<uid>). There
is currently no support for situations where the ticket file is in a
different place, such as when the user logged in via SSH and has
delegated credentials from that login. This restriction is also
present in Solaris and Linux. In theory, we could improve this in
future, possibly using Brooks Davis' implementation of variant
symlinks.
Supporting RPCSEC_GSS on a server is nearly as simple. You must create
service creds for the server in the form 'nfs/<fqdn>@<REALM>' and
install them in /etc/krb5.keytab. The standard heimdal utility ktutil
makes this fairly easy. After the service creds have been created, you
can add a '-sec=krb5' option to /etc/exports and restart both mountd
and nfsd.
The only other difference an administrator should notice is that nfsd
doesn't fork to create service threads any more. In normal operation,
there will be two nfsd processes, one in userland waiting for TCP
connections and one in the kernel handling requests. The latter
process will create as many kthreads as required - these should be
visible via 'top -H'. The code has some support for varying the number
of service threads according to load but initially at least, nfsd uses
a fixed number of threads according to the value supplied to its '-n'
option.
Sponsored by: Isilon Systems
MFC after: 1 month
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
|
|
|
| |
- we don't have ne(4), replace it with re(4)
- fix markup
- bump date
Submitted by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
- advise to use rc script to SIGHUP mountd
- add information about possiblity of using /prefix network notation [1]
PR: docs/124373
Reviewed by: jhb
Obtained from: NetBSD [1]
MFC after: 3 days
|
|
|
|
|
|
|
| |
They are no longer needed now that we filter out MNT_ROOTFS
inside the nmount() call in revision 1.267 of vfs_mount.c.
Reviewed by: rink
|
|
|
|
|
| |
case where mountd would fail to start with "out of memory" logged to
syslog.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
-h bindip
Specify specific IP addresses to bind to for TCP and UDP requests.
This option may be specified multiple times. If no -h option is
specified, mountd will bind to INADDR_ANY. Note that when specifying
IP addresses with -h, mountd will automatically add 127.0.0.1 and if
IPv6 is enabled, ::1 to the list.
PR: bin/114097
Reviewed by: pjd (an eariler version of the patch)
MFC after: 1 week
|
| |
|
|
|
|
| |
prettier.
|
|
|
|
|
|
|
| |
ZFS, where we have automatically generated /etc/zfs/exports file, which
should not be edited directly.
Discussed with: rwatson
|
|
|
|
| |
add the errmsg string returned by nmount().
|
|
|
|
|
|
| |
PR: 81230
Submitted by: Dmitrij Tejblum <tejblum yandex-team ru>
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
| |
change fixes this.
Reported by: Lin Jui-Nan Eric < ericlin dot jnlin at gmail dot com >
Submitted by: Erik Trulsson < ertr1013 at student dot uu dot se > (commit is inspired by a patch from Erik)
Pointyhat to: me
Reviewed by: stable@
Approved by: imp (mentor)
MFC after: 3 days
|
|
|
|
|
|
| |
Approved by: imp (mentor)
Sponsored by: Quality Service Provider BV
MFC after: 3 days
|
|
|
|
|
| |
PR: bin/99873
Submitted by: Danny Braniss <danny at cs dot huji dot ac dot il>
|
|
|
|
|
|
|
|
| |
parameter to try to delete an NFS export. It won't work, and will log
a spurious warning to syslog.
Tested by: Arno J. Klaassen <arno at heho dot snv dot jussieu dot fr>
MFC after: 3 days
|
|
|
|
|
| |
This eliminates spurious log entries for trying to delete exports
for filesystems like devfs and procfs.
|
|
|
|
|
|
| |
and cd9660.
PR: bin/97642
|
|
|
|
| |
on ufs, cd9660, msdosfs, and ntfs, but not all dependencies.
|
|
|
|
|
|
|
|
| |
controlling terminal.
PR: docs/96660
Submitted by: Jeff Ito <ijk@speakeasy.net>
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
them for reading. When user can open file for reading, he can also
flock(2) it, which can lead to confusions.
Pointed out by: green
|
|
|
|
| |
anymore.
|
|
|
|
|
| |
NI_WITHSCOPEID, and our getaddrinfo(3) does nothing special
for it, now.
|
| |
|
| |
|
| |
|
|
|
|
| |
PR: 56646
|
|
|
|
| |
(with permission of addtional copyright holders where appropriate)
|
| |
|
| |
|
|
|
|
|
|
|
| |
PR: docs/45371
Submitted by: Mattias Pantzare <pantzer@ludd.luth.se>,
Matthew D. Fuller <fullermd@over-yonder.net>
MFC after: 2 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that this provokes. "Wherever possible" means "In the kernel OR NOT
C++" (implying C).
There are places where (void *) pointers are not valid, such as for
function pointers, but in the special case of (void *)0, agreement
settles on it being OK.
Most of the fixes were NULL where an integer zero was needed; many
of the fixes were NULL where ascii <nul> ('\0') was needed, and a
few were just "other".
Tested on: i386 sparc64
|
|
|
|
|
|
|
| |
a known port for use in firewall rulesets; otherwise the port is chosen
at run-time by bindresvport().
MFC after: 1 week
|
| |
|
| |
|
|
|
|
| |
It is now WARNS=2 clean again.
|
|
|
|
|
|
|
|
| |
sockets in the printf.
Fix two minor co-located whitespace glitches.
Product of: France
|
| |
|
|
|
|
|
|
|
|
| |
produce backcompatible code.
Reviewed by: rwatson
Obtained from: NetBSD
MFC after: 1 day
|
| |
|
|
|
|
| |
Approved by: re
|
|
|
|
|
| |
Add FBSDID
Reorder #if/#endif around sccsid to conform style(9)
|
| |
|
|
|
|
|
|
| |
BSD 4.4. Nuke mention of Kerberos from the documentation here.
MFC after: 1 week
|
|
|
|
| |
here since some time, kldload() is used instead.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
attempting to export the non-root of a filesystem with -alldirs. This
pilot error seems to be very common, and the "could not remount" error
message doesn't give much hints about the real reason. See the old PR
below for an example.
While i was at it, make it possible to entirely omit the often
annoying error message in that case by specifying the "quiet" exports
flag. This allows to specify something like
/cdrom -alldirs,ro,quiet <where to export to>
which will silently fail if nothing is mounted under /cdrom, but do
the rigth thing as soon as you mount something.
While doing this, i've put the embedded example in the exports(5) man
page into a subsection of its own as it ought to be.
Thanks for Paul Southworth for reminding me about this problem.
PR: bin/4448
MFC after: 1 month
|
|
|
|
|
|
|
| |
size of the response.
PR: misc/26320
MFC After: 2 weeks
|
| |
|