1
1
.TH SLAPO-PCACHE 5 "RELEASEDATE" "OpenLDAP LDVERSION"
2
.\" Copyright 1998-2008 The OpenLDAP Foundation, All Rights Reserved.
2
.\" Copyright 1998-2009 The OpenLDAP Foundation, All Rights Reserved.
3
3
.\" Copying restrictions apply. See the COPYRIGHT file.
4
4
.\" Copyright 2001, Pierangelo Masarati, All rights reserved. <ando@sys-net.it>
5
.\" $OpenLDAP: pkg/ldap/doc/man/man5/slapo-pcache.5,v 1.14.2.5 2008/07/08 21:13:31 quanah Exp $
5
.\" $OpenLDAP: pkg/ldap/doc/man/man5/slapo-pcache.5,v 1.14.2.10 2009/06/03 01:41:59 quanah Exp $
7
slapo-pcache \- proxycache overlay to slapd
7
slapo\-pcache \- proxycache overlay to slapd
72
.B proxyattrset <index> <attrs...>
73
Used to associate a set of attributes <attrs..> with an <index>. Each attribute
74
set is associated with an integer from 0 to <numattrsets>\-1. These indices are
75
used by the \fBproxytemplate\fP directive to define cacheable templates.
76
A set of attributes cannot be empty. A set of attributes can contain the
77
special attributes "*" (all user attributes), "+" (all operational attributes)
78
or both; in the latter case, any other attribute is redundant and should
79
be avoided for clarity. A set of attributes can contain "1.1" as the only
80
attribute; in this case, only the presence of the entries is cached.
72
83
.B proxycachequeries <queries>
73
84
Specify the maximum number of queries to cache. The default is 10000.
87
.B proxycheckcacheability { TRUE | FALSE }
88
Check whether the results of a query being cached can actually be returned
89
from the cache by the proxy DSA. When enabled, the entries being returned
90
while caching the results of a query are checked to ensure consistency
91
with the schema known to the proxy DSA. In case of failure, the query
92
is not cached. By default, the check is off.
76
95
.B proxysavequeries { TRUE | FALSE }
77
96
Specify whether the cached queries should be saved across restarts
78
97
of the caching proxy, to provide hot startup of the cache. Only non-expired
91
110
overlay configuration changed, this feature should not be affected.
94
.B proxyattrset <index> <attrs...>
95
Used to associate a set of attributes <attrs..> with an <index>. Each attribute
96
set is associated with an integer from 0 to <numattrsets>-1. These indices are
97
used by the \fBproxytemplate\fP directive to define cacheable templates.
98
A set of attributes cannot be empty. A set of attributes can contain the
99
special attributes "*" (all user attributes), "+" (all operational attributes)
100
or both; in the latter case, any other attribute is redundant and should
101
be avoided for clarity. A set of attributes can contain "1.1" as the only
102
attribute; in this case, only the presence of the entries is cached.
105
113
.B proxytemplate <template_string> <attrset_index> <ttl> [<negttl> [<limitttl>]]
106
114
Specifies a cacheable template and "time to live" <ttl> of queries
107
115
belonging to the template. An optional <negttl> can be used to specify
113
121
Results hitting a sizelimit are not cached by default (<limitttl> set to 0).
116
.B response-callback { head | tail }
124
.B response\-callback { head | tail }
117
125
Specifies whether the response callback should be placed at the
119
127
(the default) or at the
182
190
attribute because the underlying database that actually caches the entries
183
191
may need it for optimal local processing of the queries.
193
The proxy server should contain all the schema information required for caching.
194
Significantly, it needs the schema of attributes used in the query templates.
195
If the objectClass attribute is used in a query template, it needs the definition
196
of the objectClasses of the entries it is supposed to cache.
197
It is the responsibility of the proxy administrator to keep the proxy schema
198
lined up with that of the proxied server.
185
200
Another potential (and subtle) inconsistency may occur when data is retrieved
186
201
with different identities and specific per-identity access control
187
202
is enforced by the remote server.