Quoting Tony Earnshaw <tonni@???>:
> > > Then i just replaced the /usr/sbin/exim binary with the one i have
> > > compiled, and i get messages as below. What file is not found? > > > Apr 6 02:02:00 statler exim[5289]: 2002-04-06 02:02:00 exim 3.36
> > > daemon started: pid=5289, -q30m, listening for SMTP on port 25
> > > Apr 6 02:02:00 statler exim[5290]: 2002-04-06 02:02:00 exec of
> > > exim -q failed: No such file or directory > > How about exim itself? You said you placed exim in /usr/sbin/exim...
> > is that where you configured it to be at compile time? (that's not
> > it's default path) > No, that's not right the right track. Exim has in fact been started: > > > daemon started: pid=5289, -q30m, listening for SMTP on port 25
The daemon was started as pid 5289 it succeeded as it was run by running
the exim executable, then it tried to start the first queue runner by
calling itself with -q. Whenever exim calls itself, it uses it's compiled
path (or the one specified in the config file if any). The call to execute
exim -q inside a child process (pid 5290) did not succeed with a file not
found. This error message comes from the forked child failing it's exec
not from the new called exim so the exec failed -> exim_path is most
probably set wrong.
