I have small problem with postfix when trying to switch to mysql for postfix.
I used:
$sudo postmap -q [EMAIL PROTECTED] hash:/etc/postfix/virtual
[EMAIL PROTECTED]
$sudo postmap -q [EMAIL PROTECTED]
mysql:/etc/postfix/mysql-list.cf mysql:/etc/postfix/mysql.cf
[EMAIL PROTECTED]
to test the
Jes Andersen wrote:
found out it was a chroot problem.
My fix if any comes by the same problem was to add this to the startup script:
if [ -e /var/run/mysqld/mysqld.sock ]; then
if [ -e /var/spool/postfix/var/run/mysqld/mysqld.sock ]; th$
rm /var/spool/postfix/var/run/mysqld/mysqld.sock
use TCP instead of creating mysql sockets all around your fs.
I'll rather have the higher efficiency from a unix socket and besides
my mysql is network disabled ;)
Even looking for a way to handle some caching of the response. Also
working on a more push based system, but I don't like the need
Jes Andersen wrote:
use TCP instead of creating mysql sockets all around your fs.
I'll rather have the higher efficiency from a unix socket and besides
my mysql is network disabled ;)
Then use DOS. your unix is spending too much time switching contexts and
checking permissions.
Do you
Then use DOS. your unix is spending too much time switching contexts and
checking permissions.
Do you have actual measurements or are you just speculating? the benefits of
a tcp connection generally outweight the handshake costs. and with
connection caching, the handshake costs are
