Hi Marc and Mark, Thank you for your messages.
| 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. This was approximately a correct fix. However, creating an empty directory resulted in # dpkg-reconfigure exim chown: cannot access `/var/spool/exim/db/*': No such file or directory db_upgrade: /var/spool/exim/db/*: No such file or directory db_upgrade: DB->upgrade: /var/spool/exim/db/*: No such file or directory # So, instead, I removed retry.lockfile and wait-remote_smtp.lockfile from the original directory and then "dpkg-reconfigure exim" worked. Thanks. | > 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. Thanks for the advice. I've just switched to exim4, which seems to be working. Regards, Ryo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
