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:41:50 -0400
commit4e4af74eb08df42eeb25fc99071176857a67a919 (patch)
tree137f71d119241ef1f046c3efd46c1338eee59854
parent4ba1fa74ea380d738ee6426b7c226e78619a1ad8 (diff)
downloadsssd_unused-4e4af74eb08df42eeb25fc99071176857a67a919.tar.gz
sssd_unused-4e4af74eb08df42eeb25fc99071176857a67a919.tar.xz
sssd_unused-4e4af74eb08df42eeb25fc99071176857a67a919.zip
Do not attempt to resolve nameless serverssssd-1.5.1-24.el6
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 4967e195..613efc05 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)));