| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/183681 docs/183681
Submitted by: Robin Hahling <robin.hahling@gw-computing.net>
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
Noticed by: mckusick
|
|
|
|
|
|
| |
- Add -, to SYNOPSIS section.
MFC after: 2 weeks
|
|
|
|
|
|
| |
Rework block count calculations to work correctly with small "block" sizes.
MFC after: 14 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
using the non-monetary separator returned by localeconv(3), typically
a comma or period.
MFC after: 14 days
|
|
|
|
|
|
| |
PR: bin/165321
Approved by: gjb
MFC after: 3 days
|
|
|
|
|
|
|
| |
PR: bin/165321
Submitted by: jhs
Approved by: bcr
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
| |
Base 10 is always used for the inode counts as I could not think of any
reason base 2 inode counts would be useful.
Minor mdoc markup fix to df(1) while here anyway.
MFC after: 3 weeks
|
|
|
|
|
|
|
| |
will be included in output.
Reviewed and tested by: keramida
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Sort standard sections in the (documented) preferred order.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
invalid information will be printed if the -t flag is specified.
$ df -t ufs
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 495726 139944 316124 31% /
/dev/ad0s1e 253678 6438 226946 3% /tmp
/dev/ad0s1f 56206340 13594248 38115586 26% /usr
/dev/ad0s1d 694126 19812 618784 3% /var
/dev/ad0s1d 694126 19812 618784 3% /var
$
Note that the mount point which is not accessible shows
up as the previous file system that was printed. The reason
for this is that df -t will call statfs(2) on the pathname
supplied by getfsstat(2).
This is done to refresh the file system statistics in the
event that a previous file system had a long delay in
providing its stats.
This change affects the df utility in the following ways:
o Teach df has to deal with statfs(2) failing. If statfs(2)
fails, fall back on the possibly stale stats provided by
the initial call to getfsstat(2).
o Print a warning that the fs stats could possibly be stale
o Modify the man page and document this new behavior
as a bug.
Approved by: bmilekic (mentor)
PR: 68165
|
| |
|
|
|
|
| |
Minor markup tweaks.
|
| |
|
|
|
|
|
| |
PR: 19635
Submitted by: cyrille.lefevre@laposte.net
|
|
|
|
| |
OK'ed by: imp, core
|
|
|
|
| |
since it has been fixed.
|
|
|
|
|
| |
PR: 35523
Submitted by: Tomas Svensson <tsn@gbdev.net>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/27240
Reviewed by: GAWollman
MFC after: 2 weeks
|
| |
|
| |
|
| |
|
|
|
|
| |
Approved by: jkh
|
|
|
|
|
| |
PR: 18465
Reported by: Kazu TAKAMUNE <takamune@avrl.mei.co.jp>
|
|
|
|
|
|
|
|
|
|
| |
Obtained from: parts of human readable code from OpenBSD
Reviewed by: obrien
add POSIX, byte and megabyte block size ouput flags
PR: 13579 (POSIX flag)
Submitted by: Mike Meyer <mwm@phone.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
be ignored by default by the df(1) program. This is used mostly to
avoid stat()-ing entries that do not represent "real" disk mount
points (such as those made by an automounter such as amd.) It is
also useful not to have to stat() these entries because it takes
longer to report them that for other file systems, being that these
mount points are served by a user-level file server and resulting in
several context switches. Worse, if the automounter is down
unexpectedly, a causal df(1) will hang in an interruptible way.
PR: kern/9764
Submitted by: Erez Zadok <ezk@cs.columbia.edu>
|
| |
|
|
|
|
|
|
| |
are available; suggest lsvfs(1) instead.
Reported by: Neil Blakey-Milner <nbm@rucus.ru.ac.za>
|
| |
|
|
|
|
|
|
| |
PR: 6599
Reviewed by: phk
Submitted by: Josh Gilliam <josh@quick.net>
|
| |
|
| |
|
|
|
|
|
|
| |
vfs types.
Fixed ordering of FreeBSD `k' option in synopsis.
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
| |
|
| |
|