summaryrefslogtreecommitdiffstats
path: root/sbin/mount_nfs
Commit message (Collapse)AuthorAgeFilesLines
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-102-9/+9
|
* Mechanically kill hard sentence breaks.ru2004-07-021-1/+1
|
* Remove advertising clause from University of California Regent's license,markm2004-04-092-8/+0
| | | | | | per letter dated July 22, 1999. Approved by: core, imp
* style.Makefile(5):johan2004-02-231-1/+1
| | | | Use WARNS?= instead of WARNS=.
* mdoc(7): There cannot be a subsection inside a list.ru2003-09-101-2/+4
| | | | Reported by: naddy
* mdoc(7) markup overhaul.ru2003-05-171-43/+55
|
* Remove -p from getopt args.trhodes2003-05-121-1/+1
| | | | | | | PR: 37221 Submitted by: Joshua Goodall <joshua@roughtrade.net> Reviewed by: rwatson Approved by: re (jhb)
* Remove remnants of the -p option. While I'm here, remove wording abouttrhodes2003-05-111-6/+0
| | | | | | | | -P which could be interpreted as 'this option must be specified'. PR: 37221 && 51886 Discussed with: bmah Approved by: re (blanket)
* Use __FBSDID() to quiet GCC 3.3 warnings.obrien2003-05-031-4/+4
|
* Add mount options 'noinet4' and 'noinet6' which prevent using thosemdodd2003-03-252-0/+20
| | | | | | | 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.
* - Silence warnings (casting, implicit decl., unused var.).mdodd2003-03-252-4/+7
| | | | - WARNS=2
* Update mount_nfs documentation to reference new sysctl for -c default.dillon2003-01-271-2/+6
|
* Removed a debugging printf() left here in peter'smux2002-09-141-1/+0
| | | | | | last commit. Spotted by: kris
* Bandaid for mount_nfs segfaulting with the more obscure mount optionspeter2002-09-061-22/+34
| | | | | | | | | | | | 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.
* Unbreak the -c option by not using connect(2) for mount_nfs'siedowse2002-08-261-1/+2
| | | | | | | communication with the remote NFS server if this flag is specified. PR: bin/42003 Submitted by: Jean-Luc Richier <Jean-Luc.Richier@imag.fr>
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-212-12/+12
|
* Fix -o ac(reg|dir)(min|max) options. The appropriate flags weren'tsemenu2002-08-061-0/+4
| | | | | | | | translated from ALTF_* to NFSMNT_* thus these options weren't accepted by kernel. PR: bin/30334 MFC after: 1 week
* Now that the kernel is able to load modules itself,mux2002-08-031-13/+1
| | | | | | | | | | 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.
* Convert old style (type foo *)0 casts to NULLsdillon2002-07-111-3/+3
| | | | | PR: kern/40360 Requested by: Hiten PAndya via direct email
* The .Nm utilitycharnier2002-07-061-2/+1
|
* more file system > filesystemtrhodes2002-05-161-6/+6
|
* o __P removedimp2002-03-211-5/+5
| | | | o main prototype removed
* Remove 'register' keyword.obrien2002-03-201-4/+4
| | | | | | 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?)
* Default to WARNS=2.obrien2001-12-041-0/+2
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
* note that 'nolockd' can't be used when updating mount flagsalfred2001-11-121-0/+3
|
* Allow users to use the 'nolockd' or -L options with mount_nfs in orderalfred2001-11-122-2/+26
| | | | | | 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.
* Userland part of nfs client/server split and cleanup.peter2001-09-183-250/+15
|
* mdoc(7) police: s/BSD/.Bx/ where appropriate.ru2001-08-141-3/+9
|
* Change the foreground mount behaviour so that we keep retryingiedowse2001-07-212-7/+26
| | | | | | | | | | 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
* Since revision 1.40/1.41, the default behaviour for mount_nfs isiedowse2001-07-192-12/+20
| | | | | | | | | | | | | | | | | 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.
* Remove whitespace at EOL.dd2001-07-151-1/+1
|
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-101-1/+1
|
* Use the new CLSET_CONNECT clnt_control() request on UDP clients toiedowse2001-06-231-1/+20
| | | | | | | | 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.
* Make it much more obvious that the use of NQNFS is discouraged (theiedowse2001-06-221-9/+6
| | | | | | | | | | | 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
* - Split out the {family,socktype}->netid conversion into a separateiedowse2001-05-131-11/+79
| | | | | | | | | 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.
* Fix a typo relating to the "-U" (force UDP for mount protocol)iedowse2001-04-111-6/+7
| | | | | option. When specified, make sure to use the correct netid for the getnetconfigent() call, and also in error messages.
* Split out all the RPC code into a separate function and address aiedowse2001-04-101-233/+275
| | | | | | | | | | | | | | | | | 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>
* - Back out the last (wrong) commit, and readd a modified versionache2001-03-311-84/+162
| | | | | | | | | | | | | | | | | | | | | | | | of pingnfsserver(). The pingnfsport() function is now called everytime. If we don't get RPC_SUCCESS or RPC_PROGVERSMISMATCH back, there's something wrong with the NFS server and we just exit. - Fix cfs mount on IPv4-only machines - Fixed the looping when we did not run background mode. - Fixed a getnameinfo() call with uninitialized adress. This is a NetBSD bug I didn't notified :-( Thanks Ian ! - Added some #ifdef NFSKERB - Removed some unused variables. - Fixed idention - Remove unnecessary ":" in openlog ident Submitted by: Martin Blapp <mb@imp.ch> Reviewed by: Ian Dowse <iedowse@maths.tcd.ie>
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-0/+1
| | | | - MAN[1-9] -> MAN.
* fix -o port=xxxalfred2001-03-251-5/+8
|
* Set the default manual section for sbin/ to 8.ru2001-03-201-1/+0
|
* Bring in a hybrid of SunSoft's transport-independent RPC (TI-RPC) andalfred2001-03-191-159/+137
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | associated changes that had to happen to make this possible as well as bugs fixed along the way. Bring in required TLI library routines to support this. Since we don't support TLI we've essentially copied what NetBSD has done, adding a thin layer to emulate direct the TLI calls into BSD socket calls. This is mostly from Sun's tirpc release that was made in 1994, however some fixes were backported from the 1999 release (supposedly only made available after this porting effort was underway). The submitter has agreed to continue on and bring us up to the 1999 release. Several key features are introduced with this update: Client calls are thread safe. (1999 code has server side thread safe) Updated, a more modern interface. Many userland updates were done to bring the code up to par with the recent RPC API. There is an update to the pthreads library, a function pthread_main_np() was added to emulate a function of Sun's threads library. While we're at it, bring in NetBSD's lockd, it's been far too long of a wait. New rpcbind(8) replaces portmap(8) (supporting communication over an authenticated Unix-domain socket, and by default only allowing set and unset requests over that channel). It's much more secure than the old portmapper. Umount(8), mountd(8), mount_nfs(8), nfsd(8) have also been upgraded to support TI-RPC and to support IPV6. Umount(8) is also fixed to unmount pathnames longer than 80 chars, which are currently truncated by the Kernel statfs structure. Submitted by: Martin Blapp <mb@imp.ch> Manpage review: ru Secure RPC implemented by: wpaul
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-4/+5
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-2/+2
|
* Explain why adding ``options NFSKERB'' breaks the kernel build.sheldonh2000-08-111-0/+3
| | | | | | PR: 10642 Reported by: Stefan Eggers <seggers@semyam.dinoco.de> Submitted by: johan
* Cross-reference mount_nfs(8) and showmount(8).sheldonh2000-07-181-1/+2
| | | | | PR: 20008 Reported by: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
* Order the cross-references in the SEE ALSO section, in preparationsheldonh2000-07-181-2/+2
| | | | for PR 20008.
* Fix memory leak in mount_nfs's background (-b) mode which occurs whendillon2000-06-111-2/+3
| | | | | | the mount is not available. Submitted-by: Jonathan Hanna <pangolin@home.com>
* Remove more single-space hard sentence breaks.sheldonh2000-03-021-1/+2
|
* Remove single-space hard sentence breaks. These degrade the qualitysheldonh2000-03-011-3/+6
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
OpenPOWER on IntegriCloud