Richard Pitt wrote:
> In my experience this is almost always a load issue.
> 
> I've settled on putting the database in /dev/shm - i.e. RAM disk
> 
> there is no major penalty for losing this database - on reboot for
> example - the system will simply rebuild it
> 
> Following is in my /etc/init.d/exim startup file (I run Red
> Hat/CentOS/Fedora - YMMV)
> 
> ---------------
> dev_shm() {
> # push the db into /dev/shm
> if [ -d /dev/shm/db ]
> then
>         echo "using old /dev/shm/db directory"
> else
>   mkdir -p /dev/shm/db
>   chown exim.exim /dev/shm/db
>   chmod 750 /dev/shm/db
>   mkdir -p /var/spool/exim
> fi
> cd /var/spool/exim
> rm -r db
> ln -s /dev/shm/db db
> ----------------
> 
> The dev_shm() function is called upon each startup
> 
> works for me on VERY heavily loaded systems.
> 
> richard


*trimmed*

That could be taken a step further;

- have cron set up for odd-day-even day or twice a day... whatever.

- create the new, but empty one

- move a link from old, full space to new, empty space.

- destroy the old one

Rewind 'X' time later.

Bill


-- 
## List details at http://lists.exim.org/mailman/listinfo/exim-users 
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to