> > The machine on which my svn repository lives was recently
> > upgraded. I didn't have svnserve in a run-on-reboot script,
> > so I started it by hand (log in as "svn", then type "svnserve
> > -d"). But whenever I make any requests of the server (e.g.
> > "svn ls svn://localhost", much less "svn update"), I get the
> > error message "svn: No repository found in
> > 'svn://localhost'". I then do a "ps x", and I see something like
> > 11550 ? Ss 0:00 svnserve -d
> > 11556 ? Z 0:00 [svnserve] <defunct>
> > Is 11556 just a subprocess created to handle this request,
> > which for whatever reason hasn't gone away yet? Or is it the
> > actually svn server, which for some reason died as soon as it
> > was asked to do any work?
> The former. The svnserve daemon spawns a child process for each
> connection. On UNIX derivatives, zombie processes (the Z above)
> created when a child process exits and the parent doesn't call
> wait() to
> retrieve its exit status. They get cleaned up by the init process
> > I've done an "svnadmin verify", and the repository seems to
> > be fine. None of the config files has been changed in over a
> > year, so I doubt they're corrupted. Any ideas?
> You need to tell svnserve where your repository is on the machine.
> svnserve -d -r /path/to/repo
> It's probably trying to serve a repository rooted at /, which is
> probably not where yours is.
I was going to say this, but I looked at the --help for svnserver and it doesn't seem to require the -r param. I figure it roots to the pwd. But, if he isn't running it from the repo root then yea... that!
Received on 2011-04-11 16:53:30 CEST