r64: Add missing closing bracket

[nbd.git] / nbd-server.1.sgml

diff --git a/nbd-server.1.sgml b/nbd-server.1.sgml
index d96b919..eebc7f9 100644 (file)
--- a/nbd-server.1.sgml
+++ b/nbd-server.1.sgml
@@ -55,7 +55,7 @@ manpage.1: manpage.sgml
   </refnamediv>
   <refsynopsisdiv>
     <cmdsynopsis>
-      <command>&dhpackage;</command>
+      <command>&dhpackage; </command>
 
       <arg choice=plain><replaceable>port</replaceable</arg>
       <arg choice=plain><replaceable>filename</replaceable></arg>
@@ -64,6 +64,7 @@ manpage.1: manpage.sgml
       <arg><option>-m</option></arg>
       <arg><option>-c</option></arg>
       <arg><option>-a <replaceable>timeout</replaceable></option></arg>
+      <arg><option>-l <replaceable>host list</replaceable></option></arg>
     </cmdsynopsis>
   </refsynopsisdiv>
   <refsect1>
@@ -86,7 +87,7 @@ manpage.1: manpage.sgml
     were a local filesystem.</para>
 
     <para><command>&dhpackage;</command> implements some security
-    through a file called "nbd_server.allow" in the current directory.
+    through a file called "nbd_server.allow" in the current directory (by default; a different file can be chosen with the '-l' option).
     This file must list the IP-addresses of clients that are allowed
     to connect. If it does not exist, all clients are able to connect.
     If the file is empty, no clients can connect.</para>
@@ -144,6 +145,18 @@ manpage.1: manpage.sgml
            Linux 2.2 and below), you can use this option to store the
            data in multiple files and export a larger filesystem, if
            needed.</para>
+         <para>
+           To use this option, you must create a number of files
+           with names in the format "name.X", where "name" is given as
+           the filename argument to nbd-server, and "X" is a number
+           starting by 0 and going up for each file.
+         </para>
+         <para>
+           The files must all be 1GB in size.
+         </para>
+         <para>
+           Allowing more flexibility for this option is planned for
+           future versions.</para>
        </listitem>
       </varlistentry>
       <varlistentry>
@@ -168,7 +181,22 @@ manpage.1: manpage.sgml
          this option is strongly recommended.</para>
        </listitem>
       </varlistentry>
+      <varlistentry>
+       <term><option>host list</option></term>
+       <listitem>
+         <para>This argument should contain a list of IP-addresses
+         for hosts that may connect to the server. Wildcards are
+         <emphasis>not</emphasis> allowed. If the file does not
+         exist, it is ignored (and any host can connect); If the file
+         does exist, but is empty, no host can connect. By default,
+         the name 'nbd_server.allow' is used, and looked for in the
+         current directory, unless nbd-server is compiled as a
+         daemon, in which case it is looked for in the
+         root-directory.</para>
+       </listitem>
+      </varlistentry>
     </variablelist>
+
   </refsect1>
   <refsect1>
     <title>EXAMPLES</title>
@@ -192,31 +220,19 @@ manpage.1: manpage.sgml
     </itemizedlist>
   </refsect1>
   <refsect1>
-    <title>FILES</title>
-    
-    <variablelist>
-      <varlistentry>
-       <term><filename>nbd_server.allow</filename></term>
-       <listitem>
-         <para>This file, which must be in the directory where
-         nbd-server is invoked, can contain a list of IP-addresses
-         for hosts that may connect to the server. Wildcards are
-         <b>not</b> allowed.
-       </listitem>
-      </varlistentry>
-    </variablelist>
-
-  </refsect1>
-  <refsect1>
     <title>SEE ALSO</title>
 
-    <para>nbd-client (8).</para>
+    <para>nbd-client (8), http://nbd.sourceforge.net/roadmap.html</para>
 
   </refsect1>
   <refsect1>
     <title>AUTHOR</title>
-    <para>The NBD kernel module and the NBD tools were written by
-      Pavel Machek (pavel@ucw.cz)</para>
+    <para>The NBD kernel module and the NBD tools were originally
+      written by Pavel Machek (pavel@ucw.cz)</para>
+
+    <para>The kernel module is now maintained by Paul Clements
+      (Paul.Clements@steeleye.com), while the userland tools are
+      maintained by &dhusername; (&dhemail;)</para>
 
     <para>This manual page was written by &dhusername; (&dhemail;) for
       the &debian; system (but may be used by others).  Permission is