On Tue, 23 Apr 2002, Richard Welty wrote:
> well, it didn't used to pick up the new one; the child that was spun off
> used to get the same one as the parent.
>
> this could have changed. better review the recent change log entries.
Richard, there is some confusion here; what you have stated isn't right.
A new exec of Exim has always read the config file again - there's too
much state information to pass any other way. However, if Exim just
forks without re-execing, it doesn't re-read the config file. So, for
example, a daemon reads the config, and then uses that config for every
reception process it spins off. However, when a reception process forks
a delivery process that re-execs (to regain privilege), the config is
re-read.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
