Fix deletion error logging for DB4 backend
authorJonathan McDowell <noodles@earth.li>
Wed, 11 Apr 2012 05:11:32 +0000 (22:11 -0700)
committerJonathan McDowell <noodles@earth.li>
Wed, 11 Apr 2012 05:11:32 +0000 (22:11 -0700)
  The change to include the keyid failed to remove some commas on the
  format string, meaning the output was even less useful.

keydb_db4.c

index 4e35bff934264bb8467bed73866a19d79b269f89..d3caa37be9480ce4056aa68edf1f9fc38a789246 100644 (file)
@@ -952,7 +952,7 @@ static int db4_delete_key(uint64_t keyid, bool intrans)
 
                if (ret != 0) {
                        logthing(LOGTHING_ERROR,
-                               "Problem deleting short keyid: %s ",
+                               "Problem deleting short keyid: %s "
                                "(0x%016" PRIX64 ")",
                                db_strerror(ret),
                                keyid);
@@ -984,7 +984,7 @@ static int db4_delete_key(uint64_t keyid, bool intrans)
 
                        if (ret != 0) {
                                logthing(LOGTHING_ERROR,
-                                       "Problem deleting short keyid: %s ",
+                                       "Problem deleting short keyid: %s "
                                        "(0x%016" PRIX64 ")",
                                        db_strerror(ret),
                                        keyid);
@@ -1027,7 +1027,7 @@ static int db4_delete_key(uint64_t keyid, bool intrans)
 
                if (ret != 0) {
                        logthing(LOGTHING_ERROR,
-                               "Problem deleting skshash: %s ",
+                               "Problem deleting skshash: %s "
                                "(0x%016" PRIX64 ")",
                                db_strerror(ret),
                                keyid);