Seth Woolley's Man Viewer

scache(8) - scache - Postfix shared connection cache server - man 8 scache

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

SCACHE(8)                                                            SCACHE(8)

       scache - Postfix shared connection cache server

       scache [generic Postfix daemon options]

       The  scache(8)  server  maintains a shared multi-connection cache. This
       information can be used by, for example, Postfix SMTP clients or  other
       Postfix delivery agents.

       The connection cache is organized into logical destination names, phys-
       ical endpoint names, and connections.

       As a specific example, logical SMTP  destinations  specify  (transport,
       domain,  port),  and  physical  SMTP  endpoints  specify (transport, IP
       address, port).  An SMTP connection may be  saved  after  a  successful
       mail(1,8) transaction.

       In  the general case, one logical destination may refer to zero or more
       physical endpoints, one physical endpoint may be referenced by zero  or
       more  logical  destinations, and one endpoint may refer to zero or more

       The exact syntax of a logical destination or endpoint name is  applica-
       tion  dependent;  the  scache(8) server does not care.  A connection is
       stored as a file(1,n) descriptor together with application-dependent  infor-
       mation  that  is  needed to re-activate a connection object. Again, the
       scache(8) server is completely unaware of the details of that  informa-

       All  information  is stored with a finite time(1,2,n) to live (ttl).  The con-
       nection cache  daemon  terminates  when  no  client  is  connected  for
       max_idle time(1,2,n) units.

       This server implements the following requests:

       save_endp ttl endpoint endpoint_properties file_descriptor
              Save  the specified file(1,n) descriptor and connection property data
              under the specified endpoint name. The endpoint  properties  are
              used  by  the  client  to  re-activate  a  passivated connection

       find_endp endpoint
              Look up cached properties and a cached file(1,n) descriptor  for  the
              specified endpoint.

       save_dest ttl destination destination_properties endpoint
              Save  the  binding between a logical destination and an endpoint
              under the destination name, together with  destination  specific
              connection  properties.  The  destination properties are used by
              the client to re-activate a passivated connection object.

       find_dest destination
              Look up cached destination properties, cached  endpoint  proper-
              ties,  and  a  cached  file(1,n) descriptor for the specified logical

       The scache(8) server is not security-sensitive. It does not talk to the
       network, and it does not talk to local users.  The scache(8) server can
       run chrooted at fixed low privilege.

       The scache(8) server is not a trusted process. It must not be  used  to
       store information that is security sensitive.

       Problems and transactions are logged to syslogd(8).

       The session cache cannot be shared among multiple machines.

       When  a  connection  expires  from  the cache, it is closed without the
       appropriate protocol specific handshake.

       Changes to are picked up automatically as  scache(8)  processes
       run for only a limited amount of time. Use the command "postfix reload"
       to speed up a change.

       The text below provides only a parameter summary. See  postconf(1,5)(5)  for
       more details including examples.

       connection_cache_ttl_limit (2s)
              The  maximal  time-to-live  value  that the scache(8) connection
              cache server allows.

       connection_cache_status_update_time (600s)
              How frequently the scache(8) server logs usage  statistics  with
              connection cache hit and miss rates for logical destinations and
              for physical endpoints.

       config_directory (see 'postconf(1,5) -d' output)
              The default location of the Postfix and  con-
              figuration files.

       daemon_timeout (18000s)
              How  much  time(1,2,n)  a  Postfix  daemon process may take to handle a
              request before it is terminated by a built-in watchdog(5,8) timer.

       ipc_timeout (3600s)
              The time(1,2,n) limit for sending  or  receiving  information  over  an
              internal communication channel.

       max_idle (100s)
              The  maximum  amount of time(1,2,n) that an idle Postfix daemon process
              waits for the next service request before exiting.

       process_id (read-only)
              The process ID of a Postfix command or daemon process.

       process_name (read-only)
              The process name of a Postfix command or daemon process.

       syslog_facility (mail(1,8))
              The syslog(2,3,5,3 Sys::Syslog) facility of Postfix logging.

       syslog_name (postfix)
              The mail(1,8) system name that is prepended to the  process  name  in(1,8)
              syslog(2,3,5,3 Sys::Syslog)  records,  so  that  "smtpd" becomes, for example, "post-

       smtp(8), SMTP client
       postconf(1,5)(5), configuration parameters
       master(5,8)(8), process manager
       syslogd(8), system logging

       Use "postconf(1,5) readme_directory" or "postconf(1,5) html_directory" to  locate
       this information.
       CONNECTION_CACHE_README, Postfix connection cache

       The Secure Mailer license must be distributed with this software.

       This service was introduced with Postfix version(1,3,5) 2.2.

       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA


References for this manual (incoming links)