Commit 6d91d270 authored by Max Kellermann's avatar Max Kellermann

doc/user: more NFS instructions

parent dd1cec41
...@@ -1440,7 +1440,7 @@ buffer_size: 16384</programlisting> ...@@ -1440,7 +1440,7 @@ buffer_size: 16384</programlisting>
</para> </para>
</section> </section>
<section> <section id="nfs_storage">
<title><varname>nfs</varname></title> <title><varname>nfs</varname></title>
<para> <para>
...@@ -1450,6 +1450,26 @@ buffer_size: 16384</programlisting> ...@@ -1450,6 +1450,26 @@ buffer_size: 16384</programlisting>
url="http://tools.ietf.org/html/rfc2224">RFC2224</ulink>, url="http://tools.ietf.org/html/rfc2224">RFC2224</ulink>,
for example "<parameter>nfs://servername/path</parameter>". for example "<parameter>nfs://servername/path</parameter>".
</para> </para>
<para>
This plugin uses <ulink
url="https://github.com/sahlberg/libnfs"><filename>libnfs</filename></ulink>,
which supports only NFS version 3. Since
<application>MPD</application> is not allowed to bind to
"privileged ports", the NFS server needs to enable the
"insecure" setting; example
<filename>/etc/exports</filename>:
</para>
<programlisting>/srv/mp3 192.168.1.55(ro,insecure)</programlisting>
<para>
Don't fear: "insecure" does not mean that your NFS server is
insecure. A few decades ago, people thought the concept of
"privileged ports" would make network services "secure",
which was a fallacy. The absence of this obsolete
"security" measure means little.
</para>
</section> </section>
</section> </section>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment