diff options
author | Jakub Hrozek <jhrozek@redhat.com> | 2014-04-19 19:49:21 +0200 |
---|---|---|
committer | Jakub Hrozek <jhrozek@redhat.com> | 2014-06-03 13:31:26 +0200 |
commit | 78512c471e3fd70811ad9def888778aec0f492dc (patch) | |
tree | bb6b92138b120bdc6a7a38deca04ed6199f6c44f /src/responder/ifp/ifp_iface.xml | |
parent | 2c3fa3a3264c957957db48c6c488049b6cf8b7a1 (diff) | |
download | sssd-78512c471e3fd70811ad9def888778aec0f492dc.tar.gz sssd-78512c471e3fd70811ad9def888778aec0f492dc.tar.xz sssd-78512c471e3fd70811ad9def888778aec0f492dc.zip |
IFP: Initialize negative cache timeout
In order to avoid hitting the back end with repetitive requests, the
InfoPipe responder needs a negative cache, too. This patch follows the
convention set by other responders, where the negative cache timeouts are
read from the [nss] section. This is not ideal, however, and ticket #2318
tracks moving the configuration to the [ifp] section primarily.
The timeout is also a separate parameter in the NSS context. We should
consider moving it to the negcache context instead (#2317).
Reviewed-by: Pavel Březina <pbrezina@redhat.com>
Reviewed-by: Stef Walter <stefw@redhat.com>
(cherry picked from commit 6cbb9f0d7c6be2cd3553dcb548984bb98926d5cb)
Diffstat (limited to 'src/responder/ifp/ifp_iface.xml')
0 files changed, 0 insertions, 0 deletions