On Apr 22, 2005, at 1:30 PM, Jason Mills wrote:
> Ben Collins-Sussman wrote:
>> Firedaemon is like unix inetd, right? It launches svnserve only when
>> a connection comes in? In which case, you *don't* want to use the -d
>> switch with svnserve. That causes the process to detatch into the
>> background.
>> I suspect what's going on is that firedaemon then loses track of the
>> process, thinks it's "dead" and then forcibly kills the process...
>> which of course, is guaranteed to wedge a repository. Try either
>> running 'svnserve -d' (without using Firedaemon at all), or tell
>> Firedaemon to run 'svnserve -r'.
>
> Running without -d results in the client displaying the following
> error:
> "Can't connect to host blal: No connection could be made because the
> target machine actively refused."
>
> Given that, I suspect -d is required when using FireDaemon and
> svnserve.
>
> I will try svnserver -d from the command line and see how that works
> (or use SVNService as recommended in another post).
>
Well, the question here is: why does FireDaemon decide to kill
svnserve? That's most likely what's wedging the repository, leaving
the database in an inconsistent state.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 22 20:48:20 2005