summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Pritchard <mpp@FreeBSD.org>1996-05-31 21:02:16 +0000
committerMike Pritchard <mpp@FreeBSD.org>1996-05-31 21:02:16 +0000
commit7994d1fef8fcfc88f9ce7949b2018c63cec6670c (patch)
tree6f21a6a123e93bdc62527dbe3ed943a00b6e0847
parent53df9ccfca95e08bac68c7531bf8f4b50f209544 (diff)
Notes
-rw-r--r--share/man/man4/update.414
1 files changed, 10 insertions, 4 deletions
diff --git a/share/man/man4/update.4 b/share/man/man4/update.4
index 8db326d559ce..faaf35301a07 100644
--- a/share/man/man4/update.4
+++ b/share/man/man4/update.4
@@ -37,7 +37,7 @@
.Os FreeBSD
.Sh NAME
.Nm update
-.Nd flush internal filesystem caches to disk frequently
+.Nd flush internal filesystem caches to disk periodically
.Sh SYNOPSIS
.Nm update
.Sh DESCRIPTION
@@ -46,7 +46,12 @@ The
kernel process helps protect the integrity of disk volumes
by flushing
volatile cached filesystem data
-to disk at thirty second intervals.
+to disk. This is done at thirty second intervals by default.
+The time period may be changed by using
+.Xr sysctl 8
+to modify the
+.Va kern.update
+variable.
The
.Nm update
process does the equivalent of the
@@ -57,12 +62,13 @@ function call to do the task.
.Xr fsck 8 ,
.Xr init 8 ,
.Xr rc 8 ,
-.Xr sync 8
+.Xr sync 8 ,
+.Xr sysctl 8
.Sh BUGS
It is possible on some systems that a
.Xr sync
occurring simultaneously with a crash may cause
-file system damage. See
+file system damage. See
.Xr fsck 8 .
.Sh HISTORY
An