----- Original Message -----
From: "John W. Baxter" <jwblist@???>
To: <Exim-users@???>
Sent: Wednesday, April 14, 2004 7:05 AM
Subject: Re: [Exim] Exim fails to get write lock on db files
> On 4/13/2004 16:34, "Jon Armitage" <jon.armitage@???>
wrote:
>
> > I have just built Exim 4.31 on my company's mail server with a view to
> > upgrading from 3.x. The system is running on RedHat 7.0.
> >
> > Exim compiled and installed without complaints, but when I send a test
> > message, I get (among the normal messages, not shown):
> >
> > Failed to get write lock for /var/spool/exim/db/retry.lockfile: Invalid
> > argument
> > Failed to get write lock for
/var/spool/exim/db/wait-remote_smtp.lockfile:
> > Invalid argument
>
> It appears that you are letting the new, test, Exim run in the same spool
> directory as your live old Exim. I think I would prefer not to do that
(we
> do our early testing on a different machine, which eliminates that issue).
>
> --John
>
Sorry, I should have said more clearly that I have kept the two builds
entirely separate. I still get the complaints if I shut down the production
version and run the new one as a daemon.
Jon
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (
http://www.grisoft.com).
Version: 6.0.654 / Virus Database: 419 - Release Date: 07/04/2004
