severity 377295 normal
thanks
Marc Haber wrote:
On Fri, Jul 07, 2006 at 02:32:04PM -1000, Ryo Furue wrote:
bash# dpkg-reconfigure exim
db_upgrade: /var/spool/exim/db/retry.lockfile: unrecognized file type
db_upgrade: DB->upgrade: /var/spool/exim/db/retry.lockfile: Invalid argument
bash#
I marked this bug as "grave" but I actually don't know how
severe this error is. All I can say is that exim *seems* to
continue to be working, but . . .
This is the usual berkeley DB foo. Try moving /var/spool/exim/db away,
creating an empty directory, and see whether this helps.
Not entirely. There's a bug here that it tries to check all files in the
directory, including the lockfile. I ought to write a more complicated
pattern so it ignores lock files. However, there shouldn't ordinarily be
a lock file there as exim isn't running - something must have crashed
and left it perhaps?
All errors from the database upgrade are ignored, so this will have no
effect on whether exim runs properly, so this is not really a problem.
However the error message sounds bad, so this will confuse people and
ought to be fixed. I will do something about it if and when I do another
exim package.
And, please take a look at the new Description of the exim 3 package,
consider that it might disappear from Debian any time soon, and update
to exim4.
I second this excellent advice. Despite maintaining the exim 3 packages,
I have run exim4 on my own server for years.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
