Date: Tue, 7 Sep 2004 12:25:53 -0400 From: Joe Altman <fj@panix.com> To: Matthew Seaman <m.seaman@infracaninophile.co.uk>, freebsd-questions@freebsd.org Subject: Re: [another "me too"] Re: portindex/portindexdb Message-ID: <20040907162553.GB18878@panix.com> In-Reply-To: <20040907062449.GA41144@happy-idiot-talk.infracaninophile.co.uk> References: <7A727F81-FCE2-11D8-8BE7-000A95EFF4CA@foolishgames.com> <008901c4934e$a7c5b260$0200000a@SAGEAME> <413B5F14.6090405@zonnet.nl> <200409051452.06236.donaldj1066@fastmail.fm> <413C0FAE.1000502@zonnet.nl> <20040907003500.GA11100@panix.com> <413D39D7.6050009@zonnet.nl> <20040907062449.GA41144@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040907162553.GB18878>