| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This is for better compatibility with other environments (Linux, Solaris,
HP-UX, AIX and Tru64 support these options).
PR: bin/109924
MFC after: 1 week
|
|
|
|
| |
Suggested by: rees
|
|
|
|
|
|
|
|
|
|
|
| |
If argv[0] == "mount_nfs4", then default to mounting NFSv4,
otherwise if argv[0] == "mount_nfs", default to the old mount_nfs behavior.
- Add a -4 option.
- Add the University of Michigan copyright from mount_nfs4.c, for the
code merged from mount_nfs4.c.
Reviewed by: rees
|
|
|
|
|
|
|
|
| |
This will allow the NFS mount code to return a string error message
in addition to returning an error integer value.
Reviewed by: mohans
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
the "_nfs" part of argv[0]. This should facilitate unifying mount_nfs
and mount_nfs4 into one binary.
MFC after: 1 month
Reviewed by: mohans
|
| |
|
| |
|
|
|
|
| |
Reviewed by: mohans
|
|
|
|
| |
Hinted by: bmah
|
| |
|
|
|
|
|
|
|
| |
as I know, Sun's NFS support works with TCP just fine. This is even
hinted at in the PR.
PR: 71782
|
|
|
|
| |
of the macro.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
use of the macro in sbin/mount*'s, by replacing:
mopts[] = {
MOPT_STDOPTS,
{ NULL }
}
With:
mopts[] = {
MOPT_STDOPTS,
MOPT_NULL
}
This change will help to reduce the situation that we don't explicitly
initialize "struct mntopt"'s. It should not contribute to any
functional/logical changes as far as I can tell.
|
| |
|
| |
|
|
|
|
|
|
| |
per letter dated July 22, 1999.
Approved by: core, imp
|
|
|
|
| |
Use WARNS?= instead of WARNS=.
|
|
|
|
| |
Reported by: naddy
|
| |
|
|
|
|
|
|
|
| |
PR: 37221
Submitted by: Joshua Goodall <joshua@roughtrade.net>
Reviewed by: rwatson
Approved by: re (jhb)
|
|
|
|
|
|
|
|
| |
-P which could be interpreted as 'this option must be specified'.
PR: 37221 && 51886
Discussed with: bmah
Approved by: re (blanket)
|
| |
|
|
|
|
|
|
|
| |
address families.
This is useful for preventing NFS mounts from using IPv6 on hosts
that have both A and AAAA records for the same name.
|
|
|
|
| |
- WARNS=2
|
| |
|
|
|
|
|
|
| |
last commit.
Spotted by: kris
|
|
|
|
|
|
|
|
|
|
|
|
| |
in /etc/fstab. This isn't a real fix though and I'm still not sure
why it started failing. mount(8) breaks up the nfs args into seperate
repeated '-o option=value' arguments. But, the altflags variable that
we use to track things is incrementally built up each time we see the
next option and shows us the cumulative set of flags, not just the
flag that we are currently looking at. As a result, the strstr hack
for looking up flags in a giant -o opt=val,opt=val, etc string was failing
and causing a segfault. I do not know what changed recently that caused
this to suddenly break, but the code has been rather bogus for some time.
|
|
|
|
|
|
|
| |
communication with the remote NFS server if this flag is specified.
PR: bin/42003
Submitted by: Jean-Luc Richier <Jean-Luc.Richier@imag.fr>
|
| |
|
|
|
|
|
|
|
|
| |
translated from ALTF_* to NFSMNT_* thus these options weren't accepted
by kernel.
PR: bin/30334
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
remove all the code which was trying to do so.
This code was nasty in several ways, it was hiding
the kernel bug where the kernel was unable to properly
load a module, and it was quitting if it wasn't able
to load the module. The consequence is that an ABI
breakage of the vfsconf API would have broken *every*
mount utility.
|
|
|
|
|
| |
PR: kern/40360
Requested by: Hiten PAndya via direct email
|
| |
|
| |
|
|
|
|
| |
o main prototype removed
|
|
|
|
|
|
| |
It does not help modern compilers, and some may take some hit from it.
(I also found several functions that listed *every* of its 10 local vars with
"register" -- just how many free registers do people think machines have?)
|
|
|
|
|
|
| |
Binary builds that cannot handle this must explicitly set WARNS=0.
Reviewed by: mike
|
| |
|
|
|
|
|
|
| |
to avoid the need for rpc.lockd to perform client locks. Using
this option a user can revert back to using local locks for NFS mounts
like we did before we had rpc.lockd.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
forever by default. This matches what mount_nfs did before revision
1.40, and it is the generally expected behaviour for NFS mounts.
Document the current defaults near the start of the man page and
mention the options that can be used to change them.
Discussed on: -hackers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to give up after one attempt unless a background mount is requested.
Background mounts would retry 10000 times (at least 7 days) before
giving up.
For some situations such as diskless terminals, an NFS filesystem
may be critical to the boot process, so neither the "try once" nor
background mounts are appropiate. To cater for this situation,
unbreak the -R (retry count) parameter so that it also works in
the non-background case. Interpret a zero retry count as "retry
forever".
The defaults are now "try once" for non-background mounts and "retry
forever" for background mounts; both can be overridden via -R.
Add a description of this behaviour to the manpage.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
ensure that we never proceed with the mount() syscall if the server
is replying from the wrong source address. Previously the userland
RPC call to the remote nfsd would succeed, but the kernel uses
connect() so it would not see the replies, resulting in a hung
mount.
|
|
|
|
|
|
|
|
|
|
|
| |
NQNFS code is ancient, bug-ridden, and should probably be removed).
The wording here was very confusing; it was easy to get the impression
that NQNFS is an extension to NFSv3 when in fact it just uses some
NFSv3-like extensions on top of NFSv2. As witnessed by the mailing
lists and PRs, some people were reading the description and deciding
that NQNFS was what they wanted to use.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
function; we now handle unknown protocols more gracefully.
- Cache the return from getnetconfigent() so that we don't have to
remember to call freenetconfigent() each time. This fixes a memory
leak that would cause retrying background mount_nfs processes to
slowly increase their memory usage.
|
|
|
|
|
| |
option. When specified, make sure to use the correct netid for the
getnetconfigent() call, and also in error messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
number of issues:
- Fix background mounts; these were broken in revision 1.40.
- Don't give up before trying all addresses returned by getaddrinfo().
- Use protocol-independent routines where possible.
- Improve error reporting for RPC errors.
- In non-background mode, give up after trying all protocols once.
- Use daemon(3) instead of rolling our own version.
- Never go ahead with the mount() syscall until we have received
a reply from the remote nfsd; this is especially important with
non-interruptible mounts, as otherwise a mistyped command might
require a reboot to correct.
Reviewed by: alfred, Martin Blapp <mb@imp.ch>
|