Re: What does txn-current-lock do?

Okay, Andrey, I don't want to get into any arguments here, but didn't
you do EXACTLY THE SAME thing in the first place? You quoted my
listing of the db/ directory and then made this very vague comment.

What were you referring to when you said "the worst way from
administration point of view..."? the fact that these files were on a
775 permission? or the fact that these files were owned by different
users? or the fact that we access our repository using svn+ssh? or the
fact that usernames were user1, user2, and so on? (if so, that was
intentionally done because I didn't want to reveal the actual
usernames).

If you are kind enough to go back to my original message and read it
again, you will see that I was trying to find out why the lock file
was owned by different user. what should the correct umask and
permission be for this file? You failed to elaborate, and that is not
helpful. It's the same as if some software crashed, and you say "it
has a bad bug and take care of the bug".

-- Jim

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2385067

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-19 03:46:37 CEST