Date: Wed, 9 Apr 2014 15:54:46 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44507 - head/en_US.ISO8859-1/books/handbook/disks Message-ID: <201404091554.s39FskoO008960@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Wed Apr 9 15:54:45 2014 New Revision: 44507 URL: http://svnweb.freebsd.org/changeset/doc/44507 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Apr 9 15:41:54 2014 (r44506) +++ head/en_US.ISO8859-1/books/handbook/disks/chapter.xml Wed Apr 9 15:54:45 2014 (r44507) @@ -2420,13 +2420,11 @@ Filesystem 1K-blocks Used Avail Capacity </indexterm> <indexterm><primary>disk quotas</primary></indexterm> - <para>Disk quotas - can be used to limit the amount of disk space or the number of - files a user or members of a group may allocate on a per-file - system basis. This prevents one user or - group of users from consuming all of the available disk - space.</para> - + <para>Disk quotas can be used to limit the amount of disk space or + the number of files a user or members of a group may allocate on + a per-file system basis. This prevents one user or group of + users from consuming all of the available disk space.</para> + <para>This section describes how to configure disk quotas for the <acronym>UFS</acronym> file system. To configure quotas on the <acronym>ZFS</acronym> file system, refer to <xref @@ -2442,13 +2440,13 @@ Filesystem 1K-blocks Used Avail Capacity kern.features.ufs_quota: 1</screen> <para>In this example, the <literal>1</literal> indicates quota - support. If the value is instead <literal>0</literal>, - add the following line to a custom kernel configuration file - and rebuild the kernel using the instructions in <xref + support. If the value is instead <literal>0</literal>, add + the following line to a custom kernel configuration file and + rebuild the kernel using the instructions in <xref linkend="kernelconfig"/>:</para> <programlisting>options QUOTA</programlisting> - + <para>Next, enable disk quotas in <filename>/etc/rc.conf</filename>:</para> @@ -2458,41 +2456,40 @@ kern.features.ufs_quota: 1</screen> <primary>disk quotas</primary> <secondary>checking</secondary> </indexterm> - <para>Normally on bootup, the - quota integrity of each file system is checked by - &man.quotacheck.8;. This program insures that the data in the - quota database properly reflects the data on the file system. - This is a time consuming process that will significantly - affect the time the system takes to boot. To skip this step, - add this variable to <filename>/etc/rc.conf</filename>:</para> + <para>Normally on bootup, the quota integrity of each file + system is checked by &man.quotacheck.8;. This program insures + that the data in the quota database properly reflects the data + on the file system. This is a time consuming process that + will significantly affect the time the system takes to boot. + To skip this step, add this variable to + <filename>/etc/rc.conf</filename>:</para> <programlisting>check_quotas="NO"</programlisting> <para>Finally, edit <filename>/etc/fstab</filename> to enable - disk quotas on a per-file system basis. To enable per-user quotas on a file system, add - <option>userquota</option> to the options field in the - <filename>/etc/fstab</filename> entry for the file system to - enable quotas on. For example:</para> + disk quotas on a per-file system basis. To enable per-user + quotas on a file system, add <option>userquota</option> to the + options field in the <filename>/etc/fstab</filename> entry for + the file system to enable quotas on. For example:</para> <programlisting>/dev/da1s2g /home ufs rw,userquota 1 2</programlisting> - <para>To enable group quotas, use - <option>groupquota</option> instead. To enable both user and group - quotas, separate the options with a comma:</para> + <para>To enable group quotas, use <option>groupquota</option> + instead. To enable both user and group quotas, separate the + options with a comma:</para> <programlisting>/dev/da1s2g /home ufs rw,userquota,groupquota 1 2</programlisting> - <para>By default, quota files are stored in the root - directory of the file system as - <filename>quota.user</filename> and + <para>By default, quota files are stored in the root directory + of the file system as <filename>quota.user</filename> and <filename>quota.group</filename>. Refer to &man.fstab.5; for more information. Specifying an alternate location for the quota files is not recommended.</para> <para>Once the configuration is complete, reboot the system and - <filename>/etc/rc</filename> will - automatically run the appropriate commands to create the - initial quota files for all of the quotas enabled in + <filename>/etc/rc</filename> will automatically run the + appropriate commands to create the initial quota files for all + of the quotas enabled in <filename>/etc/fstab</filename>.</para> <para>In the normal course of operations, there should be no @@ -2545,11 +2542,11 @@ kern.features.ufs_quota: 1</screen> are allowed. When the user drops back below the soft limit, the grace period is reset.</para> - <para>In the following example, the quota for the - <systemitem class="username">test</systemitem> account is being edited. - When <command>edquota</command> is invoked, the editor specified by - <envar>EDITOR</envar> is opened in order to edit the quota - limits. The default editor is set to + <para>In the following example, the quota for the <systemitem + class="username">test</systemitem> account is being edited. + When <command>edquota</command> is invoked, the editor + specified by <envar>EDITOR</envar> is opened in order to edit + the quota limits. The default editor is set to <application>vi</application>.</para> <screen>&prompt.root; <userinput>edquota -u test</userinput> @@ -2559,13 +2556,14 @@ Quotas for user test: /usr/var: kbytes in use: 0, limits (soft = 50, hard = 75) inodes in use: 0, limits (soft = 50, hard = 60)</screen> - <para>There are normally two lines for each file system that - has quotas enabled. One line represents the block limits and - the other represents the inode limits. Change the value to - modify the quota limit. For example, to raise the - block limit on <filename>/usr</filename> - to a soft limit of <literal>500</literal> and a hard limit of <literal>600</literal>, - change the values in that line as follows:</para> + <para>There are normally two lines for each file system that has + quotas enabled. One line represents the block limits and the + other represents the inode limits. Change the value to modify + the quota limit. For example, to raise the block limit on + <filename>/usr</filename> to a soft limit of + <literal>500</literal> and a hard limit of + <literal>600</literal>, change the values in that line as + follows:</para> <programlisting>/usr: kbytes in use: 65, limits (soft = 500, hard = 600)</programlisting> @@ -2573,11 +2571,11 @@ Quotas for user test: editor.</para> <para>Sometimes it is desirable to set quota limits on a range - of users. This can be done by first assigning the desired quota limit to a - user. Then, use <option>-p</option> to duplicate that quota - to a specified range of user IDs (<acronym>UID</acronym>s). - The following command will duplicate - those quota limits for <acronym>UID</acronym>s + of users. This can be done by first assigning the desired + quota limit to a user. Then, use <option>-p</option> to + duplicate that quota to a specified range of user IDs + (<acronym>UID</acronym>s). The following command will + duplicate those quota limits for <acronym>UID</acronym>s <literal>10,000</literal> through <literal>19,999</literal>:</para> @@ -2594,21 +2592,20 @@ Quotas for user test: <secondary>checking</secondary> </indexterm> - <para>To check individual user - or group quotas and disk usage, use &man.quota.1;. A user - may only examine their own quota and the quota of a group they - are a member of. Only the superuser may view all user and - group quotas. To get a summary of all quotas and disk usage - for file systems with quotas enabled, use - &man.repquota.8;.</para> + <para>To check individual user or group quotas and disk usage, + use &man.quota.1;. A user may only examine their own quota + and the quota of a group they are a member of. Only the + superuser may view all user and group quotas. To get a + summary of all quotas and disk usage for file systems with + quotas enabled, use &man.repquota.8;.</para> <para>Normally, file systems that the user is not using any disk - space on will not show in the output of <command>quota</command>, even if - the user has a quota limit assigned for that file system. Use - <option>-v</option> to display those file systems. The - following is sample output from - <command>quota -v</command> for a user that has quota limits - on two file systems.</para> + space on will not show in the output of + <command>quota</command>, even if the user has a quota limit + assigned for that file system. Use <option>-v</option> to + display those file systems. The following is sample output + from <command>quota -v</command> for a user that has quota + limits on two file systems.</para> <programlisting>Disk quotas for user test (uid 1002): Filesystem usage quota limit grace files quota limit grace @@ -2629,11 +2626,11 @@ Quotas for user test: <indexterm><primary>NFS</primary></indexterm> - <para>Quotas are enforced by the quota subsystem on the <acronym>NFS</acronym> - server. The &man.rpc.rquotad.8; daemon makes quota - information available to <command>quota</command> on <acronym>NFS</acronym> clients, - allowing users on those machines to see their quota - statistics.</para> + <para>Quotas are enforced by the quota subsystem on the + <acronym>NFS</acronym> server. The &man.rpc.rquotad.8; daemon + makes quota information available to <command>quota</command> + on <acronym>NFS</acronym> clients, allowing users on those + machines to see their quota statistics.</para> <para>On the <acronym>NFS</acronym> server, enable <command>rpc.rquotad</command> by removing the @@ -3203,30 +3200,28 @@ geli_da2_flags="-p -k /root/da2.key"</pr <para>Like the encryption of disk partitions, encryption of swap space is used to protect sensitive information. Consider an application that deals with passwords. As long as these - passwords stay in physical memory, they are not - written to disk and will be cleared after a reboot. However, if &os; starts - swapping out memory pages to free space, - the passwords may be written to the disk unencrypted. - Encrypting swap space can be a solution for this - scenario.</para> - - <para>This section demonstrates how to configure an encrypted - swap partition using &man.gbde.8; or &man.geli.8; encryption. - It assumes a <acronym>UFS</acronym> file system where - <filename>/dev/ad0s1b</filename> is the swap - partition.</para> + passwords stay in physical memory, they are not written to disk + and will be cleared after a reboot. However, if &os; starts + swapping out memory pages to free space, the passwords may be + written to the disk unencrypted. Encrypting swap space can be a + solution for this scenario.</para> + + <para>This section demonstrates how to configure an encrypted + swap partition using &man.gbde.8; or &man.geli.8; encryption. + It assumes a <acronym>UFS</acronym> file system where + <filename>/dev/ad0s1b</filename> is the swap partition.</para> <sect2> <title>Configuring Encrypted Swap</title> - <para>Swap partitions are not encrypted by default and should - be cleared of any sensitive data before continuing. To - overwrite the current swap partition with random garbage, - execute the following command:</para> + <para>Swap partitions are not encrypted by default and should be + cleared of any sensitive data before continuing. To overwrite + the current swap partition with random garbage, execute the + following command:</para> - <screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/<replaceable>ad0s1b</replaceable> bs=1m</userinput></screen> + <screen>&prompt.root; <userinput>dd if=/dev/random of=/dev/<replaceable>ad0s1b</replaceable> bs=1m</userinput></screen> - <para>To encrypt the swap partition using &man.gbde.8;, add the + <para>To encrypt the swap partition using &man.gbde.8;, add the <literal>.bde</literal> suffix to the swap line in <filename>/etc/fstab</filename>:</para> @@ -3240,19 +3235,18 @@ geli_da2_flags="-p -k /root/da2.key"</pr <programlisting># Device Mountpoint FStype Options Dump Pass# /dev/ad0s1b.eli none swap sw 0 0</programlisting> - <para>By default, &man.geli.8; uses the <acronym>AES</acronym> algorithm - with a key length of 128 bit. These defaults can - be altered by using <literal>geli_swap_flags</literal> in - <filename>/etc/rc.conf</filename>. The following flags configure - encryption using the Blowfish algorithm with - a key length of 128 bits and a sectorsize of 4 kilobytes, and - sets <quote>detach on last close</quote>:</para> + <para>By default, &man.geli.8; uses the <acronym>AES</acronym> + algorithm with a key length of 128 bit. These defaults can be + altered by using <literal>geli_swap_flags</literal> in + <filename>/etc/rc.conf</filename>. The following flags + configure encryption using the Blowfish algorithm with a key + length of 128 bits and a sectorsize of 4 kilobytes, and sets + <quote>detach on last close</quote>:</para> <programlisting>geli_swap_flags="-e blowfish -l 128 -s 4096 -d"</programlisting> - <para>Refer to the description of - <literal>onetime</literal> in &man.geli.8; for a list of - possible options.</para> + <para>Refer to the description of <literal>onetime</literal> in + &man.geli.8; for a list of possible options.</para> </sect2> <sect2>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201404091554.s39FskoO008960>