summaryrefslogtreecommitdiffstats
path: root/sbin/umount
Commit message (Collapse)AuthorAgeFilesLines
* Explicitly add more files to the 'runtime' package.gjb2016-02-091-0/+1
| | | | Sponsored by: The FreeBSD Foundation
* Fix type mismatches for malloc(3) and Co.uqs2015-12-291-1/+1
| | | | | | Found by: clang static analyzer Reviewed by: ed Differential Revision: https://reviews.freebsd.org/D4722
* Document that a forced dismount of an NFSv3 mount when thermacklem2015-06-171-1/+4
| | | | | | | | | NLM (rpc.lockd) is running can crash the system. Unfortunately this is not easy to fix, but I have left PR#200585 open. PR: 200585 MFC after: 3 days
* Add META_MODE support.sjg2015-06-131-0/+20
|\ | | | | | | | | | | | | | | | | | | | | Off by default, build behaves normally. WITH_META_MODE we get auto objdir creation, the ability to start build from anywhere in the tree. Still need to add real targets under targets/ to build packages. Differential Revision: D2796 Reviewed by: brooks imp
| * dirdeps.mk now sets DEP_RELDIRsjg2015-06-081-2/+0
| |
| * Merge sync of headsjg2015-05-271-1/+2
| |\ | |/ |/|
| * Merge from head@274682sjg2014-11-191-1/+1
| |\
| * | Updated dependenciessjg2014-05-161-1/+0
| | |
| * | Updated dependenciessjg2014-05-101-0/+2
| | |
| * | Updated dependenciessjg2013-03-111-0/+1
| | |
| * | Updated dependenciessjg2013-02-161-2/+0
| | |
| * | Sync with HEAD.obrien2013-02-081-3/+10
| |\ \
| * | | Sync FreeBSD's bmake branch with Juniper's internal bmake branch.marcel2012-08-221-0/+21
| | | | | | | | | | | | | | | | Requested by: Simon Gerraty <sjg@juniper.net>
* | | | Cross-reference autounmountd(8) from umount(8).trasz2014-11-221-1/+2
| |_|/ |/| | | | | | | | | | | MFC after: 1 month Sponsored by: The FreeBSD Foundation
* | | Use mount protocol version 3 by default for showmount and umount.peter2014-08-161-1/+1
| |/ |/| | | | | | | | | mount_nfs effectively uses mount protocol v3 by default already. v1 mount protocol is being removed along with nfsv2 by a high profile NFS appliance vendor and our legacy v1 mount protocol usage causes rpc errors.
* | Fix memory leak in umount.ceadler2012-11-151-3/+10
|/ | | | | | | PR: bin/172553 Submitted by: Erik Cederstrand <erik@cederstrand.dk> Approved by: cperciva MFC after: 3 days
* Add missing static keywords for global variables to tools in sbin/.ed2011-11-041-3/+3
| | | | | | These tools declare global variables without using the static keyword, even though their use is limited to a single C-file, or without placing an extern declaration of them in the proper header file.
* When using -A option (unmount all mounted filesystems), do not attemptmckusick2011-07-141-0/+2
| | | | to unmount /dev as it will always fail.
* Add a sentence to the umount.8 man page to clarify the behaviourrmacklem2011-05-311-1/+4
| | | | | | | | for forced dismount when used on an NFS mount point. Requested by Jeremy Chadwick. This is a content change. MFC after: 2 weeks
* Modify the umount(8) command so that it doesn't dormacklem2011-05-291-3/+4
| | | | | | | | | | | | | a sync(2) syscall before unmount(2) for the "-f" case. This avoids a forced dismount from getting stuck for an NFS mountpoint in sync() when the server is not responsive. With this commit, forced dismounts should normally work for the NFS clients, but can take up to about 1minute to complete. PR: kern/157365 Reviewed by: kib MFC after: 2 weeks
* It's possible to unmount multiple items at once, make it clear.ru2011-03-242-2/+2
|
* Introduce '[ipaddr]:path' notation.ume2010-02-041-3/+10
| | | | | | | | | | | Since the existing implementation searches ':' backward, a path which includes ':' could not be mounted. You can now mount such path by enclosing an IP address by '[]'. Though we should change to search ':' forward, it will break 'ipv6addr:path' which is currently working. So, it still searches ':' backward, at least for now. MFC after: 2 weeks
* Let umount build with -Wold-style-definition.ed2009-12-301-1/+1
|
* Make umount(8) WARNS=6 clean:delphij2009-12-282-28/+28
| | | | | | | | | | | - Cast delimiter width to integer [1] - Solve name conflicts against system header - Constify parameters to avoid qualifier conflict PR: bin/140017 [1] Submitted by: Ulrich Spörlein <uqs spoerlein net> [1] MFC after: 1 month Sponsored by: iXsystems, Inc
* Be more precise how to get fsids - 'mount -v' doesn't show fsids unless is runpjd2009-08-171-1/+2
| | | | | | by root. Approved by: re (kib)
* Don't use sys/nfs/rpcv2.h - it is part of the old kernel RPC implementationdfr2009-06-241-5/+5
| | | | and will be removed.
* Sync program's usage() with manpage's SYNOPSIS.ru2005-02-101-2/+2
|
* 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
* s/considred/considered/brueffer2004-03-041-1/+1
|
* style.Makefile(5):johan2004-02-231-1/+1
| | | | Use WARNS?= instead of WARNS=.
* Don't include the file system ID in the output of `mount -v' if itiedowse2003-12-051-3/+4
| | | | | | | | | is all zeros. The kernel now consistently zeroes FSIDs for non-root users, so there's no point in printing these. Also fix a misspelling in a comment. Submitted by: Rudolf Cejka <cejkar@fit.vutbr.cz> Approved by: re (scottl)
* If the unmount by file system ID fails, don't warn before retryingiedowse2003-11-161-1/+4
| | | | | | | a non-fsid unmount if the file system ID is all zeros. This is a temporary workaround for warnings that occur in the vfs.usermount=1 case because non-root users get a zeroed filesystem ID. I have a more complete fix in the works, but I won't get it done for 5.2.
* When removing trailing slashes, don't remove the first characteriedowse2003-10-291-3/+3
| | | | | of the name if it is '/'. Also fix a comparison between signed and unsigned quantities (pointed out by trhodes).
* Take advantage of the use of file system IDs to simplify umount(8)iedowse2003-07-201-298/+144
| | | | | | | | | | | | | | | | | and make it work more reliably in a number of cases that have traditionally been troublesome. The new behaviour is: 1) If the filesystem can be determined by the fsid or device, or uniquely identified by the mountpoint, then just go ahead and call unmount(2) using the file system ID. 2) Otherwise use fstatfs(2) to resolve the path into a file system ID (checking with stat(2) that it is a filesystem root directory). Case 2 can potentially block if an NFS server is down, but it can always be avoided by using an unambiguous specification. It handles all the hard cases such as symlinks and mismatches between the mount list and reality. For example, if a filesystem was mounted as /mnt inside a chroot, it will show up in the mount list as /mnt, but now you can unmount it from outside the chroot with "umount /chroot_path/mnt".
* When mount(8) is invoked with the `-v' flag, display the filesystemiedowse2003-07-182-16/+50
| | | | | | | | | | | | ID for each file system in addition to the normal information. In umount(8), accept filesystem IDs as well as the usual device and path names. This makes it possible to unambiguously specify which file system is to be unmounted even when two or more file systems share the same device and mountpoint names (e.g. NFS mounts from the same export into different chroots). Suggested by: Dan Nelson <dnelson@allantgroup.com>
* Since checkmntlist() and getmntentry() return a struct statfs thatiedowse2003-07-181-24/+17
| | | | includes the filesystem type name, remove the "type" output parameter.
* When the file system to unmount is specified by device name insteadiedowse2003-07-181-45/+7
| | | | | | | | of by mount point, umount had to take care not to unmount the wrong file system if another file system was covering the requested one. Now that the file system to unmount is specified to the kernel using the filesystem ID, this confusion cannot occur, so remove the code that checked for it.
* Add a new mount flag MNT_BYFSID that can be used to unmount a fileiedowse2003-07-011-70/+71
| | | | | | | | | | | | | | | | | | system by specifying the file system ID instead of a path. Use this by default in umount(8). This avoids the need to perform any vnode operations to look up the mount point, so it makes it possible to unmount a file system whose root vnode cannot be looked up (e.g. due to a dead NFS server, or a file system that has become detached from the hierarchy because an underlying file system was unmounted). It also provides an unambiguous way to specify which file system is to be unmunted. Since the ability to unmount using a path name is retained only for compatibility, that case now just uses a simple string comparison of the supplied path against f_mntonname of each mounted file system. Discussed on: freebsd-arch mdoc help from: ru
* mdoc(7) fixes: Fix the markup in the recently added ENVIRONMENT section.ru2003-05-191-6/+6
|
* Bump the date for recent commits.mdodd2003-04-071-1/+1
|
* Clarify the behavior of PATH_FSTAB with regard to 'tainted' execution.mdodd2003-04-071-0/+7
| | | | Requested by: ru
* Implement the '-F' option for mount & umount which allows the user tomdodd2003-04-072-3/+18
| | | | specify an alternate fstab file.
* Quiet warning.mdodd2003-04-071-2/+2
|
* Remove one of two WARNS=0.johan2003-02-231-1/+0
|
* Correct typos, mostly s/ a / an / where appropriate. Some whitespace cleanup,schweikh2003-01-011-2/+2
| | | | especially in troff files.
* s/filesystem/file system/g as discussed on -developerstrhodes2002-08-212-19/+19
|
* - Introduce a new struct xvfsconf, the userland version of struct vfsconf.mux2002-08-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | - Make getvfsbyname() take a struct xvfsconf *. - Convert several consumers of getvfsbyname() to use struct xvfsconf. - Correct the getvfsbyname.3 manpage. - Create a new vfs.conflist sysctl to dump all the struct xvfsconf in the kernel, and rewrite getvfsbyname() to use this instead of the weird existing API. - Convert some {set,get,end}vfsent() consumers to use the new vfs.conflist sysctl. - Convert a vfsload() call in nfsiod.c to kldload() and remove the useless vfsisloadable() and endvfsent() calls. - Add a warning printf() in vfs_sysctl() to tell people they are using an old userland. After these changes, it's possible to modify struct vfsconf without breaking the binary compatibility. Please note that these changes don't break this compatibility either. When bp will have updated mount_smbfs(8) with the patch I sent him, there will be no more consumers of the {set,get,end}vfsent(), vfsisloadable() and vfsload() API, and I will promptly delete it.
* The .Nm utility.charnier2002-07-061-3/+2
|
* more file system > filesystemtrhodes2002-05-161-3/+3
|
* Default to WARNS=2.obrien2001-12-041-0/+3
| | | | | | Binary builds that cannot handle this must explicitly set WARNS=0. Reviewed by: mike
OpenPOWER on IntegriCloud