Nuutti, I am SO in agreement here. It seems that by far, the two most
common newbie problems are
1. "Help, my repository isn't responding anymore."
2. "Help, my working copy says it's locked."
These problems have similar explanations, so I think I'll add a new
FAQ to the "troubleshooting" section. It will be easier to point
people there.
Nuutti Kotivuori <naked@iki.fi> writes:
> Over time, I have noticed that quite nearly every new user (I've
> counted over 5 who I have discussed with personally) who manages to
> wedge their repository first tells that the database was *corrupted*
> and that he was able to recover it, though.
>
> Now this isn't entirely incorrect ofcourse - but certainly confuses
> the hell out of me every time it happens.
>
> There's two things that could use a visible and good explanation,
> perhaps in the FAQ.
>
> 1) Most of the time when a program that's directly using the
> repository gets killed, it will wedge the repository. This is the
> current status and may be better in the future.
>
> 2) Wedging is a really really mild case of corruption - usually it
> just means that an operation was left incomplete and that lock files
> were left around. A simple recover will make things happy again.
>
> I'd say 99% of the situations people run into these days is Ctrl-C:ing
> a local subversion process (or having it die for some reason). It
> would be good to stress that this is mostly just a minor
> inconvenience, not a reason to pull the big red-alert-data-corruption
> lever.
>
> -- Naked
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 2 15:58:12 2002