On Sun, 2004-05-02 at 09:57, Lukas Ruf wrote:
> > Ben Collins-Sussman <sussman@collab.net> [2004-04-30 18:19]:
> >
> > On Fri, 2004-04-30 at 01:47, Lukas Ruf wrote:
> >
> > > The repository is mounted via NFS (server Solaris 2.8)
> >
> > Yes, there are warnings all over creation not to do this (README, FAQ,
> > Book...) Don't do this. If you move the repository to local disk, are
> > you able to reproduce the memory leak? I'd like to know.
> >
>
> I know I should not do this. However, for a bunch of other
> repositories, there is no problem with that configuration.
"There is no problem?" Allow me to quote the book:
"If you attempt to use Berkeley DB on a network share, the results are
unpredictable—you may see mysterious errors right away, or it may be
months before you discover that your repository database is subtly
corrupted."
So you're working at your own risk here. Good luck.
>
> I copied the repository in question to the local disk and tried to
> check out the stuff via https as usual -- without success. svn
> started growing... Fortunately for me, I still have the original data
> laying around.
Sorry for the confusion here: you're talking about the svn *client*
program growing huge, right?
If so, is it possible for one of us to reproduce the problem? In other
words, can you give us a URL to checkout/update, so we can try to
witness/debug the problem firsthand?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 3 16:49:56 2004