os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Break up the description of dumpfreq' and passno' fields of fstab(5)

Browse source 
to two separate items.  The text of `passno' is a bit more verbose now
than the old one.

PR:		docs/33043
Submitted by:	Ashley Penney <ashp@unloved.org>
This commit is contained in:
Giorgos Keramidas 2002-01-11 02:50:21 +00:00
parent 1f72c2c952
commit 10a7ec0db4
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=11668
1 changed files with 21 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -535,11 +535,27 @@
<varlistentry>
<term><literal>dumpfreq</literal></term>
<listitem><para>The number of days the filesystem should be
dumped, and <literal>passno</literal> is the pass number
during which the filesystem is checked during the boot
sequence.</para>
</listitem>
<listitem><para>This is used by dump to determine which
filesystems require dumping. If the field is missing,
a value of zero is assumed.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>passno</literal></term>
<listitem>
<para>This determines the order in which filesystems should
be checked. Filesystems that should be skipped should have
their <literal>passno</literal> set to zero. The root
filesystem (which needs to be checked before everything
else) should have it's <literal>passno</literal> set to
one, and other filesystems' <literal>passno</literal>
should be set to values greater than one. If more than one
filesystems have the same <literal>passno</literal> then
&man.fsck.8; will attempt to check filesystems in parallel
if possible.</para>
</listitem>
</varlistentry>
</variablelist>
</sect2>