--- Tony Finch Writes: ---
> You're trying to run two copies of Exim. Kill the one that is already
> running before starting the new one.
If that's the case, I think I know what the culprit is, I use a crontab
entry to make sure exim is running... one I stole from eggdrop... I used to
have a problem with exim3 segfaulting on the old machine, and never took the
script from my crontab when I updated to exim4. It's also handy if you need
to kill the process to do an upgrade or something and forget to turn it back
on. I have it set to run every 5 minutes. I guess the latest exim doesn't
work properly with that script. I've commented it out of crontab for now,
and we'll see what happens.
The script is below...
-=[crd]=-
---
Computer problem and clueless as to what to do about it?
Confused by tech support's help?
Find someone locally to help!
http://www.fixmystupidpc.com
--- Script /root/smchk ---
#! /bin/sh
#
# This file checks, every minute, to make sure the sendmail server is
# running. If it isn't, it restarts the server.
#
cd /var/run
# is there a pid file?
if test -r exim.pid
then
# there is a pid file -- is it current?
smtppid=`head --lines=1 exim.pid`
if `kill -CHLD $smtppid >/dev/null 2>&1`
then
# it's still going -- back out quietly
exit 0
fi
echo ""
echo "Stale exim.pid file, erasing..."
rm -f exim.pid
fi
# test if we have run smchk previously and didn't find a userfile
echo ""
echo "Couldn't find exim running, reloading..."
echo ""
/etc/rc.d/init.d/exim start
exit 0
