Date: Sat, 2 Sep 2017 10:06:37 +0000 (UTC) From: Bjoern Heidotting <bhd@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r50784 - head/en_US.ISO8859-1/books/handbook/zfs Message-ID: <201709021006.v82A6bKC028593@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bhd Date: Sat Sep 2 10:06:37 2017 New Revision: 50784 URL: https://svnweb.freebsd.org/changeset/doc/50784 Log: Whitespace and intentation fixes. Wrap a long line. Modified: head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Fri Sep 1 14:39:13 2017 (r50783) +++ head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sat Sep 2 10:06:37 2017 (r50784) @@ -1302,7 +1302,7 @@ errors: No known data errors</screen> operating systems that support <acronym>ZFS</acronym>, and even different hardware architectures (with some caveats, see &man.zpool.8;). When a dataset has open files, - <command> zpool export -f</command> can be used to force the + <command>zpool export -f</command> can be used to force the export of a pool. Use this with caution. The datasets are forcibly unmounted, potentially resulting in unexpected behavior by the applications which had open files on those @@ -1886,21 +1886,20 @@ tank custom:costcenter - - <title>Getting and Setting Share Properties</title> <para>Two commonly used and useful dataset properties are the - <acronym>NFS</acronym> and <acronym>SMB</acronym> share options. - Setting these define if and how <acronym>ZFS</acronym> datasets - may be shared on the network. At present, only setting sharing - via <acronym>NFS</acronym> is supported on &os;. To get the - current status of a share, enter:</para> + <acronym>NFS</acronym> and <acronym>SMB</acronym> share + options. Setting these define if and how + <acronym>ZFS</acronym> datasets may be shared on the network. + At present, only setting sharing via <acronym>NFS</acronym> is + supported on &os;. To get the current status of + a share, enter:</para> <screen>&prompt.root; <userinput>zfs get sharenfs <replaceable>mypool/usr/home</replaceable></userinput> - NAME PROPERTY VALUE SOURCE - mypool/usr/home sharenfs on local +NAME PROPERTY VALUE SOURCE +mypool/usr/home sharenfs on local +&prompt.root; <userinput>zfs get sharesmb <replaceable>mypool/usr/home</replaceable></userinput> +NAME PROPERTY VALUE SOURCE +mypool/usr/home sharesmb off local</screen> - &prompt.root; <userinput>zfs get sharesmb <replaceable>mypool/usr/home</replaceable></userinput> - - NAME PROPERTY VALUE SOURCE - mypool/usr/home sharesmb off local</screen> - <para>To enable sharing of a dataset, enter:</para> <screen>&prompt.root; <userinput> zfs set sharenfs=on <replaceable>mypool/usr/home</replaceable></userinput></screen> @@ -3564,8 +3563,8 @@ vfs.zfs.vdev.cache.size="5M"</programlisting> pools can be backed by regular files, this is especially useful for testing and experimentation. Use the full path to the file as the device path - in <command>zpool create</command>. All vdevs must be - at least 128 MB in size.</para> + in <command>zpool create</command>. All vdevs + must be at least 128 MB in size.</para> </listitem> <listitem>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201709021006.v82A6bKC028593>