[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: DB_CONFIG on svn.collab.net

From: Stephen C. Tweedie <sct_at_redhat.com>
Date: 2002-05-17 18:17:55 CEST


On Fri, May 17, 2002 at 12:10:39PM -0400, Kevin Pilch-Bisson wrote:

> > At the very least, would it be possible to add some form of error
> > flagging so that when the lock limit is exceeded, we get a useful
> > error back instead of the current "out of memory" error that the user
> > sees?
> That's a good point. Where do you think such an error flag should go? It's
> not clear to me whether or not we could actually check db4 for this error
> specifically, but we could maybe make a FAQ saying "If you see ENOMEM errs,
> try this before giving up...

Hmm, it's not clear from the db4 documentation exactly which error db4
is going to return when this happens. If we could trap exactly that
error, then appending a line like

        EFOO may also indicate you need more locks in the db;
        see <url> for info

to the error output would at least prevent the user from giving up in


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 17 18:19:23 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.