resolved: properly signal transient errors back to NSS stack
authorLennart Poettering <lennart@poettering.net>
Mon, 22 Nov 2021 14:17:34 +0000 (15:17 +0100)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Tue, 11 Jan 2022 17:46:49 +0000 (18:46 +0100)
commit7ab91cb307eb0a518f4a956674a108221538fc88
tree410575738c469bcc950e297a8fbbc11b63c20760
parent70f465cb5d10b7bcd7bd7c326756d542e59c0e0b
resolved: properly signal transient errors back to NSS stack

NSS mostly knows four error cases: SUCCESS, NOTFOUND, UNAVAIL, TRYAGAIN,
and they can all be used in nsswitch.conf to route requests.

So far nss-resolve would return SUCCESS + NOTFOUND + UNAVAIL. Let's also
return TRYAGAIN in some cases, specifically the ones where we are
currntly unable to resolve a request but likely could later. i.e.
errors caused by networking issues or such.

Fixes: #20786
(cherry picked from commit ae78529fc75027b3487b64e0d22a572fd9c8ffeb)
src/nss-resolve/nss-resolve.c