Documenting valueless lxc.cap.drop behaviour

From b24b0e16848fbb93402a08efa3950cd59272b8da Mon Sep 17 00:00:00 2001
From: Marko Hauptvogel <marko.hauptvogel@googlemail.com>
Date: Sun, 3 Jan 2016 23:07:19 +0100
Subject: [PATCH] Documenting valueless lxc.cap.drop behaviour

Undocummented behaviour since 7d0eb87.

Signed-off-by: Marko Hauptvogel <marko.hauptvogel@googlemail.com>
Acked-by: Stéphane Graber <stgraber@ubuntu.com>

diff --git a/doc/lxc.container.conf.sgml.in b/doc/lxc.container.conf.sgml.in
index 16b8f2584d54c06659d3c0a39eb713a9db503834..1d44f381b5a863c56962639e6c5017c89753dba0 100644 (file)
--- a/doc/lxc.container.conf.sgml.in
+++ b/doc/lxc.container.conf.sgml.in
@@ -1015,7 +1015,9 @@ proc proc proc nodev,noexec,nosuid 0 0
               <citerefentry>
                 <refentrytitle><command>capabilities</command></refentrytitle>
                 <manvolnum>7</manvolnum>
-              </citerefentry>,
+              </citerefentry>.
+              If used with no value, lxc will clear any drop capabilities
+              specified up to this point.
             </para>
           </listitem>
         </varlistentry>