A simple way to determine who is at fault is to set
tmpdir=/usr/mysql.tmp in my.cnf.
cd /usr
mkdir mysql.tmp
chown mysql:mysql mysql.tmp
vi /usr/local/etc/my.cnf
insert or change tmpdir=/usr/mysql.tmp (this does not effect the
/tmp/mysql.sock)
/usr/local/etc/rc.d/mysql-server restart
restart dbmail daemons as well.
Test for a while and report.
Also, you should be testing with the maxconnections=100 and the patch
that Paul posted a couple of days ago.
-Jon
Andrea Brancatelli wrote:
> litio# df -h
> Filesystem Size Used Avail Capacity Mounted on
> /dev/ad1s1a 1.9G 1.1G 670M 63% /tmp
>
> litio# /usr/local/etc/rc.d/dbmail-imapd restart
> Stopping dbmail_imapd.
> Waiting for PIDS: 78180, 78180.
> Starting dbmail_imapd.
>
> litio# df -h
> Filesystem Size Used Avail Capacity Mounted on
> /dev/ad1s1a 1.9G 18K 1.8G 0% /tmp
>
>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
> ------------------------------------------------------------------------
>
> _______________________________________________
> DBmail mailing list
> [email protected]
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
