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:
parent
e09e7ac3c4
commit
2b0c1bfd8d
|
@ -232,7 +232,7 @@ enum nss_status _nss_mymachines_gethostbyname4_r(
|
||||||
fail:
|
fail:
|
||||||
UNPROTECT_ERRNO;
|
UNPROTECT_ERRNO;
|
||||||
*errnop = -r;
|
*errnop = -r;
|
||||||
*h_errnop = NO_DATA;
|
*h_errnop = NO_RECOVERY;
|
||||||
return NSS_STATUS_UNAVAIL;
|
return NSS_STATUS_UNAVAIL;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
@ -403,7 +403,7 @@ enum nss_status _nss_mymachines_gethostbyname3_r(
|
||||||
fail:
|
fail:
|
||||||
UNPROTECT_ERRNO;
|
UNPROTECT_ERRNO;
|
||||||
*errnop = -r;
|
*errnop = -r;
|
||||||
*h_errnop = NO_DATA;
|
*h_errnop = NO_RECOVERY;
|
||||||
return NSS_STATUS_UNAVAIL;
|
return NSS_STATUS_UNAVAIL;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue