On Mar 7, 2008, at 11:16, <Jason.Butlin_at_sungard.com>
<Jason.Butlin_at_sungard.com> wrote:
> We have a situation that just appeared to start happening for no
> reason what so ever. At some point during the day one of our
> repositories wouldn’t allow you commit any code.
>
> After some investigation I worked out that the SVNServe had to be
> running as an Admin user, but only for this one database. The
> others are OK. After further investigation it would appear that the
> transaction details are not being written to the db\transactions
> location. I have a pre-commit hook that copies the contents of this
> directory but comes up empty against this database.
>
> So I guess the transaction is being written to somewhere that
> requires admin access. But where is this and what’s happened to the
> database configuration to affect this changes? How to I make them
> go back to the correct location?
Sounds to me like you're jumping to confusions. Let's start over with
the basics.
What version of Subversion on the server and client? What OS on the
server and client? What error message do you see when you try to
commit? Does it still happen if you get a new working copy? Does it
still happen from a different client? Does it also happen if you
commit directly from the server? Does it also happen if you use
file:/// protocol on the server directly instead of using svn://?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-07 20:35:55 CET