Matt Saladna via Postfix-users:
> Nov 14 20:10:45 web2 postfix/proxymap[1378875]: panic: dict_db_sequence: no
> cursor
> Nov 14 20:10:46 web2 postfix/postscreen[1377623]: warning: dict_proxy_lookup:
> service proxywrite: Connection reset by peer
I do not recommend using postscreen with a proxied cache. postsreen
is latency-sensitive. There is only one postscreen process, and all
its lookups are handled by a single proxymap process that is also
shared with other processes.
With Postfix services that have a process limit > 1, the number of
proxymap processes scales up with demand.
I don't know if other databases do better when the file system fills
up. You should have a monotor that sends an alert when file system
space drops below some number.
(Alternatively Postfix lookup tables could refuse update requests
when the free space drops below some number, but that works only
if Postfix can figure out where the data lives. With LDAP, *SQL*
that will not be the case)
Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
