Re: [exim] Separate spool directories

* Jim Roberts

> Errr... Can you compile a second instance of Exim on the same machine,
> setup for a different queue (spool_directory), and set it listening on an
> unused port, and also launch queue-runners for that one, too? (They could
> even run at different intervals than the main queue-runners). Then, when
> you get a message you would prefer to be put on the alternate queue, simply
> route it to the other Exim instance, and have that one configured with
> queue_only.
>
> I also read someplace of a way to run multiple instances of Linux
> (completely separate) on the same machine, as if it were two different
> machines. Google for it. I have no clue what it was called. Sorry. But
> if you did that, you could easily run multiple copies of Exim with
> completely separate queues, on the same box.

This will work, but the problem is performance. Because you here will
have to sync the message to disk twice, while if it was directed to the
appropriate spool from the beginning it would only be saved once. And in
my experience I/O performance is /the/ bottleneck when it comes to raw
performance (unless you're doing fancy stuff as content filtering and
so on, of course).

--
Tore Anderson