On Tue, Sep 07, 2004 at 07:24:49AM +0100, Matthew Seaman wrote: > > Another workaround is simply to set: > > PORTS_DBDRIVER=bdb1_hash
This is the Berkeley, AKA Sleepycat, bdb? I ask because I am also (suddenly) encountering the famous Exim "Failed to open DBM file /var/spool/exim/db/retry for writing:" message. Oddly, until recently this error was not in evidence; and prior to recently, it was in evidence and I fixed it; prior to that failure, it (wait for it) Just Worked[1]. I wonder if the issue as evidenced by the Exim error could possibly be related to the ruby error? I hear, from time to time, vague rumblings about how the bdb software seeming to annoy people. I know one thing I've learned, and hope it is accurate: when installing Exim (and likely any other MTA as a substitute for Sendmail) build it from source the first time, because installing a binary and then using portupgrade will likely cause problems down the road. Of course, that lesson is probably covered in an FAQ somewhere, and I just forgot it. > in your environment, and then use portsdb and portupgrade as usual. > There are a number of variations on this workaround, but the other > ways of doing that involve installing some extra software. > > See: > > http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015902.html > http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015922.html Thanks; that last one looks interesting. [1] So: it worked, it failed, it worked, and now, shortly before the ruby issue, it began to fail. My previous cure for the Exim error was, vis-a-vis this last failure, ineffectual. _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"