nss-mymachines: return NO_RECOVERY instead of NO_DATA when we fail to do D-Bus and...

This makes more semantical sense and is what we do in nss-resolve in a
similar case, hence let's remove the differences here.

diff --git a/src/nss-mymachines/nss-mymachines.c b/src/nss-mymachines/nss-mymachines.c
index da3efb960abf50f44502d7c1ecbe868bd6b48f9f..0e76c4317275417e666709a1e3d5975d7234a2f9 100644 (file)
--- a/src/nss-mymachines/nss-mymachines.c
+++ b/src/nss-mymachines/nss-mymachines.c
@@ -232,7 +232,7 @@ enum nss_status _nss_mymachines_gethostbyname4_r(
 fail:
         UNPROTECT_ERRNO;
         *errnop = -r;
-        *h_errnop = NO_DATA;
+        *h_errnop = NO_RECOVERY;
         return NSS_STATUS_UNAVAIL;
 }
 
@@ -403,7 +403,7 @@ enum nss_status _nss_mymachines_gethostbyname3_r(
 fail:
         UNPROTECT_ERRNO;
         *errnop = -r;
-        *h_errnop = NO_DATA;
+        *h_errnop = NO_RECOVERY;
         return NSS_STATUS_UNAVAIL;
 }