Date: Fri, 12 Feb 2021 17:46:23 GMT From: Gordon Bergling <gbe@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 7ed46663b3 - main - FAQ: Fix a typo Message-ID: <202102121746.11CHkNKm080133@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by gbe: URL: https://cgit.FreeBSD.org/doc/commit/?id=7ed46663b384745ad9155468a8ed05114b655279 commit 7ed46663b384745ad9155468a8ed05114b655279 Author: Ceri Davies <ceri@submonkey.net> AuthorDate: 2021-02-12 17:44:14 +0000 Commit: Gordon Bergling <gbe@FreeBSD.org> CommitDate: 2021-02-12 17:44:14 +0000 FAQ: Fix a typo - witout -> without PR: 253456 Reported by: Ceri Davies <ceri at submonkey dot net> --- documentation/content/en/books/faq/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/en/books/faq/_index.adoc b/documentation/content/en/books/faq/_index.adoc index 78c24c3fdd..b3f7f1b99b 100644 --- a/documentation/content/en/books/faq/_index.adoc +++ b/documentation/content/en/books/faq/_index.adoc @@ -1230,7 +1230,7 @@ The device name used in the previous examples must be changed according to the c This is due to how these commands actually work. `du` goes through the directory tree, measures how large each file is, and presents the totals. `df` just asks the file system how much space it has left. They seem to be the same thing, but a file without a directory entry will affect `df` but not `du`. -When a program is using a file, and the file is deleted, the file is not really removed from the file system until the program stops using it. The file is immediately deleted from the directory listing, however. As an example, consider a file large enough to affect the output of `du` and `df`. A file being viewed with `more` can be deleted wihout causing an error. The entry is removed from the directory so no other program or user can access it. However, `du` shows that it is gone as it has walked the directory tree and the file is not listed. `df` shows that it is still there, as the file system knows that `more` is still using that space. Once the `more` session ends, `du` and `df` will agree. +When a program is using a file, and the file is deleted, the file is not really removed from the file system until the program stops using it. The file is immediately deleted from the directory listing, however. As an example, consider a file large enough to affect the output of `du` and `df`. A file being viewed with `more` can be deleted without causing an error. The entry is removed from the directory so no other program or user can access it. However, `du` shows that it is gone as it has walked the directory tree and the file is not listed. `df` shows that it is still there, as the file system knows that `more` is still using that space. Once the `more` session ends, `du` and `df` will agree. This situation is common on web servers. Many people set up a FreeBSD web server and forget to rotate the log files. The access log fills up [.filename]#/var#. The new administrator deletes the file, but the system still complains that the partition is full. Stopping and restarting the web server program would free the file, allowing the system to release the disk space. To prevent this from happening, set up man:newsyslog[8].
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202102121746.11CHkNKm080133>