summaryrefslogtreecommitdiffstats
path: root/sbin/mount_nfs
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Use libcrypto instead of libdes.markm2000-02-241-2/+2
|
* Changed setflags() to set_flags(). This fixes part of the world breakagebde2000-01-281-3/+3
| | | | due to recently incremented namespace pollution in <unistd.h>.
* Thresh-out the nfs manual page references a bitdillon2000-01-131-1/+3
| | | | Reviewed by: Julian Elischer <julian@elischer.org>
* Finish up umntall support. init now passed an argument to thedillon1999-11-222-63/+12
| | | | | | | | | rundown script 'reboot' or 'single'. ISO support (which never worked) has been removed from mount_nfs. mount_nfs and umount now use mounttab, which allows umntall to work properly. The rc scripts now call umntall as appropriate. Submitted by: Martin Blapp <mb@imp.ch>
* Fix an overflow or two and replace a while with a for.green1999-10-301-9/+11
| | | | Submitted by: Martin Blapp <mbr@imp.ch>
* mount* fixes from Martin Blapp <mb@imp.ch>:phk1999-10-091-13/+40
| | | | | | | | | | | | | | | | | Made mount more userfriendly (bad slashes are now filtered out) and we remove in mount_nfs trailing slashes if there are any. Fixed mount_xxx binarys to resolve with realpath(3) the mountpoint. Translate the deprecated nfs-syntax with '@' to ':' . The ':' syntax has now precedence, but '@' still works. Notify the user that the '@' syntax should not be used. PR: 7846 PR: 13692 Submitted by: Martin Blapp <mb@imp.ch> Reviewed by: phk
* Fix -Wall warningsn_hibma1999-10-081-1/+1
| | | | Submitted-By: Martin Blapp <mblapp@kassiopeja.lan.attic.ch>
* Print a warning that includes the mount source when the foregrounddillon1999-10-021-0/+1
| | | | | | | mount fails prior to going into the background when a background NFS mount is requested. PR: misc/12376
* $Id$ -> $FreeBSD$peter1999-08-282-2/+2
|
* Sync usage string and man page. Correct use of .Nm. Spelling. Removecharnier1998-07-062-23/+19
| | | | unused #includes.
* Fix bogon in man page. "-o conn" actually turns off NFSMNT_NOCONN as it isjkoshy1998-06-291-2/+2
| | | | | | | | a "negative" option. This makes it equivalent to /not/ specifying "-c". The compile time default is /not/ to have the NFSMNT_NOCONN flag set, so "-o conn" should never be needed---truly a deprecated option :-). PR: 6905.
* Support changing the attribute cache limits per-mount. We don't havepeter1998-05-192-2/+38
| | | | | many option letters left, I used long names only (like the previous port= option)
* Mention the 2GB NFS v2 filesize limit.peter1998-05-011-2/+3
| | | | | PR: 6335 Submitted by: tom@sdf.com
* Don't define KERNEL before including <nfs/nfs.h>. It is no longerbde1998-02-011-3/+1
| | | | | necessary. This fixes warnings about missing forward declarations for structs in kernel-only prototypes.
* Removed definition of _NEW_VFSCONF. The new vfsconf interface is nowbde1998-01-201-1/+0
| | | | the default.
* style(9) correctionsimp1997-12-261-3/+5
| | | | Submitted by: bde
* Be extra paranoid about trusting the length returned by gethostbyaddr.imp1997-12-241-3/+3
| | | | Submitted by: Julian Assange
* Introduce a -N option that disables the use of reserved ports, nowjoerg1997-10-192-5/+14
| | | | | | | that -P is on by default. Remove do-nothing code in the -P case (but leave the option itself for backward compatibility). PR: bin/4500
* Allow the 'async' mount flag.dfr1997-06-031-1/+2
|
* Test both the NFS and MOUNT protocols for v3 support before allowing a v3dfr1997-05-011-1/+61
| | | | | | | mount. It is possible to have v3 MOUNT but only v2 NFS, for instance for a custom user-mode server like CFS. Reviewed by: "Louis A. Mamakos" <louie@TransSys.COM>
* Use v3 protocol by default if it is supported by the server. Allow thedfr1997-04-182-11/+49
| | | | | | user to force v2 protocol even if the server supports v3. Obtained from: NetBSD but with a slightly different implementation
OpenPOWER on IntegriCloud