]> git.ipfire.org Git - thirdparty/krb5.git/commitdiff
Warn about dump -recurse nonfunctionality
authorTom Yu <tlyu@mit.edu>
Wed, 3 Aug 2016 21:00:05 +0000 (17:00 -0400)
committerTom Yu <tlyu@mit.edu>
Fri, 2 Sep 2016 22:27:04 +0000 (18:27 -0400)
kdb5_util dump -recurse hasn't behaved as documented since krb5-1.5,
when the DAL was integrated.  Restoring it is a nontrivial amount of
work, so just document it for now.

(cherry picked from commit eb8dc865efec4938d74a7955fdcd02bbee4c22b9)

ticket: 8470
version_fixed: 1.13.7

doc/admin/admin_commands/kdb5_util.rst
src/kadmin/dbutil/dump.c

index a818bb5fa75fc28c21666211be7dccc60dccf5e0..cceb179914700506da09e920d30bd54f293fd758 100644 (file)
@@ -182,6 +182,12 @@ load_dump version 7".  If filename is not specified, or is the string
     corruption, this option will probably retrieve more principals
     than the **-rev** option will.
 
+    .. note::
+        The **-recurse** option currently doesn't modify the dump
+        functionality as described above; it does a normal dump.
+
+    .. deprecated:: 1.5
+
 .. _kdb5_util_dump_end:
 
 load
index 07f62e909b0d7658657e00d91af2f00d0870afc2..253bf3f9203201b1c71497ab2fc574ac1881bc97 100644 (file)
@@ -1304,6 +1304,9 @@ dump_db(int argc, char **argv)
         } else if (!strcmp(argv[aindex], "-recurse")) {
             /* Accept this for compatibility, but do nothing since
              * krb5_db_iterate doesn't support it. */
+            fprintf(stderr,
+                    _("%s: WARNING: the -recurse option is currently "
+                      "unimplemented\n"), progname);
         } else {
             break;
         }