Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

cacheadm(1) [debian man page]

cacheadm(1)							    ShapeTools							       cacheadm(1)

NAME
cacheadm - administer and configure AtFS derived object cache SYNOPSIS
cacheadm [-Amax_cached_per_cacheattr] [-Nmax_cached_per_name] [-Tmax_total_cached] [-q] [-v] directories DESCRIPTION
cacheadm provides control over the size of a derived object cache. You may set the maximum total number (T) of derived files to be stored, the maximum number of derived files per name (N) and the maximum number of derived files with the same name and the same caching attribute (A). Called without any options, cacheadm returns the actual sizes of the derived object caches in the named dirctories. An empty list of directories causes cacheadm to operate on the current directory. The relationship of the three cache size values must always be T >= N >= A. The caching attribute mechanism is described on the af_cache(3) manual page. When calculating your caching sizes you should keep in mind that you may set the total size (T) to any value but your cache will never grow bigger than N*number_of_names. Number_of_names is the number of source object histories in your directories, where derived objects may be compiled from. If you set T to an astronomic value, the cache adapt it's size to the number of source histories automati- cally. In the current implementation, the caching sizes can only be increased. Reduction of the maximum cache size is only possible when the cache is empty. Hence you have to clean your cache (atfsrepair -C (1)) first if you want to shrink its size. OPTIONS
-A max_cached_per_cacheattr Set the maximum number of derived files with the same name and the same caching attribute to be stored. Default is 1. -N max_cached_per_name Set the maximum number of derived files with the same name to be stored. Default is 3. -T max_total_cached Set the total maximum number of derived files to be stored in the derived object cache. Default is 64. -q Quiet operation. Sup- presses any output to stdout. This option does not affect error messages (stderr). -v Output version identification string. SEE ALSO
chgrp(1), chmod(1), atfsrepair(1), af_cache(3) AUTHOR
Andreas.Lampen@cs.tu-berlin.de AtFS-1.71 Thu Jan 13 15:30:55 1994 cacheadm(1)

Check Out this Related Man Page

LDAP_CACHE(3)						     Library Functions Manual						     LDAP_CACHE(3)

NAME
ldap_enable_cache, ldap_disable_cache, ldap_destroy_cache, ldap_flush_cache, ldap_uncache_entry, ldap_uncache_request, ldap_set_cache_options - LDAP client caching routines SYNOPSIS
#include <ldap.h> ldap_enable_cache( ld, timeout, maxmem ) LDAP *ld; long timeout; long maxmem; void ldap_disable_cache( ld ) LDAP *ld; void ldap_destroy_cache( ld ) LDAP *ld; void ldap_flush_cache( ld ) LDAP *ld; void ldap_uncache_entry( ld, dn ) LDAP *ld; char *dn; void ldap_uncache_request( ld, msgid ) LDAP *ld; int msgid; void ldap_set_cache_options( ld, opts ) LDAP *ld; unsigned long opts; DESCRIPTION
These routines are used to control the behavior of the experimental client caching of ldap_search(3) and ldap_compare(3) operations. By default, the cache is disabled and no caching is done. Enabling the cache can greatly improve performance and reduce network bandwidth when a client DUA makes repeated requests. ldap_enable_cache() should be called to turn on local caching or to change cache parameters (lifetime of cached requests and memory used). The ld parameter should be the result of a successful call to ldap_open(3). The timeout is specified in seconds, and is used to decide how long to keep cached requests. The maxmem value is in bytes, and is used to set an upper bound on how memory the cache will use. You can specify 0 for maxmem to restrict the cache size by the timeout only. The first call to ldap_enable_cache creates the cache; subsequent calls re-enable the cache and set the timeout and memory values. ldap_disable_cache() temporarily disables use of the cache (new requests are not cached and the cache is not checked when returning results). It does not delete the cache contents. ldap_destroy_cache() turns off caching and completely removes the cache from memory. ldap_flush_cache() deletes the cache contents, but does not effect it in any other way. ldap_uncache_entry() removes all requests that make reference to the distinguished name dn from the cache. It should be used, for example, after doing an ldap_modify(3) call involving dn. ldap_uncache_request() removes the request indicated by the LDAP request id msgid from the cache. ldap_set_cache_options() is used to change caching behavior. The current supported options are LDAP_CACHE_OPT_CACHENOERRS to suppress caching of any requests that result in an error, and LDAP_CACHE_OPT_CACHEALLERRS to enable caching of all requests. The default behavior is to not cache requests that result in errors, except that request that result in the error LDAP_SIZELIMIT_EXCEEDED are cached. ERRORS
ldap_enable_cache() returns 0 upon success, and -1 if it is unable to allocate space for the cache. All the other calls are declared as void and return nothing. SEE ALSO
ldap(3), ldap_search(3), ldap_compare(3) ACKNOWLEDGEMENTS
OpenLDAP is developed and maintained by The OpenLDAP Project (http://www.openldap.org/). OpenLDAP is derived from University of Michigan LDAP 3.3 Release. OpenLDAP 2.0.27-Release 22 September 1998 LDAP_CACHE(3)
Man Page