summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJakub Hrozek <jhrozek@redhat.com>2011-04-01 13:33:47 +0200
committerStephen Gallagher <sgallagh@redhat.com>2011-04-01 15:36:27 -0400
commit63d85fff72563cb913287ab7785c551fa98fc35d (patch)
tree44423e1ff1d2870ae6df4d078fef6e047311e2f4
parent89e594e4c5fb392a3ec9507b3f12a4edd339c5c9 (diff)
downloadsssd-63d85fff72563cb913287ab7785c551fa98fc35d.tar.gz
sssd-63d85fff72563cb913287ab7785c551fa98fc35d.tar.xz
sssd-63d85fff72563cb913287ab7785c551fa98fc35d.zip
Do not attempt to resolve nameless servers
The failover code is not strictly in charge of resolving. Its main function is to provide a server to connect to for a service. It is legal, although not currently used, to have a server that has no name (server->common == NULL). In this case, no resolving should be done and it is assumed that the failover user, which are the SSSD back ends in our case, would perform any resolving out of band, perhaps using the user_data attribute of fo_server structure.
-rw-r--r--src/providers/fail_over.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/providers/fail_over.c b/src/providers/fail_over.c
index 4967e195c..613efc05e 100644
--- a/src/providers/fail_over.c
+++ b/src/providers/fail_over.c
@@ -312,7 +312,7 @@ get_server_status(struct fo_server *server)
time_t timeout;
if (server->common == NULL)
- return SERVER_NAME_NOT_RESOLVED;
+ return SERVER_NAME_RESOLVED;
DEBUG(7, ("Status of server '%s' is '%s'\n", SERVER_NAME(server),
str_server_status(server->common->server_status)));