</refnamediv>
<refsynopsisdiv>
<cmdsynopsis>
- <command>&dhpackage;</command>
+ <command>&dhpackage; </command>
<arg choice=plain><replaceable>port</replaceable</arg>
<arg choice=plain><replaceable>filename</replaceable></arg>
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>
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>
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.
+ root-directory.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
- </variablelist>
- </refsect1>
<refsect1>
<title>EXAMPLES</title>
<para>Some examples of nbd-server usage:</para>
<refsect1>
<title>SEE ALSO</title>
- <para>nbd-client (8).</para>
+ <para>nbd-client (8), http://nbd.sourceforge.net/roadmap.html</para>
</refsect1>
<refsect1>