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

This makes more semantical sense and is what we do in nss-resolve in a
similar case, hence let's remove the differences here.
This commit is contained in:
Lennart Poettering 2019-04-10 21:56:37 +02:00
parent e09e7ac3c4
commit 2b0c1bfd8d
1 changed files with 2 additions and 2 deletions

View File

@ -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;
}