At 12:43 +0200 8/2/2001, Sascha E. Pollok wrote:
>I am currently thinking about installing multiple instances
>of exim on one machine with own dirctory, binaries, spool directory
>and whatever and just bound them to different ip-addresses.
>
>That should work, shoudln't it?
As you state it, it should be fine (resource limits not getting in the way).
You'll have some trouble invoking the "right" Exim utility instance without
some planning...you can't for instance just type exiwhat after putting one
of the binary directories into your path.
Hmmm, I just realized something while typing the prior sentence: exiwhat
in that environment the way we are set up triggers all the processes to
report, after only clearing the exim-process.info in one of the spool
directories, and then catting that one. exiwhatXXX does the other. But
that's because the exim binary has the same leaf name...it may well be
cleaner to fix that.
What with SirCam problems, I've been doing exiwhat a lot...and our second
instance, which on average has just the daemon running, now has a 4K
exim-process.info file going back to noon on July 31 (the last time I ran
exiwhatXXX [not its name], which we have aliased to a hacked exiwhat which
reports "the other" exim instance).
You'll also have to deal with making exicyclog behave for you.
In our case, exilock cares about the same set of mail files for either
instance...it might not in your case. We don't run eximon.
--John
--
John Baxter jwblist@??? Port Ludlow, WA, USA
