RE: "can't get exclusive lock" error when attempting commit

If you are running svnserve then you should be accessing the repository using svn://newdev/svn rather than file://newdev/svn.

If you want to access the repository through apache then use http://newdev/svn.

I would only pick one method, however, and stick to it. I don't think it's a good idea to access a repository via multiple protocols (although I can't remember the reasons why).

Certainly svnserve or apache provide a more scalable solution than placing the repository on a network share and accessing it with the file:// url.
_________________________________________________________________
Keith Moore

-----Original Message-----
From: NElizaga [mailto:ne_at_planitagency.com]
Sent: Thursday, 22 May 2008 11:21
To: users_at_subversion.tigris.org
Subject: RE: "can't get exclusive lock" error when attempting commit

The funny thing is the machine is already running Apache, as well as the
svnserve service ;) I followed this guide:
http://www.ivantodorov.com/blog/?p=28
Are there specific steps to hook svnsever + Apache together?

The path to the network drive is //newdev/SVN, so naturally I assumed it
would work like so: svn://newdev/SVN. No such luck, however. I suppose I
should ask our IT guy... which in itself is a bad idea, mainly the reason
I'm doing this and he's not haha. I had asked him about looking into SVN and
his response was basically "open source software sucks". Nice.

Thanks for you help!

-nick

kepboy999 wrote:
>
> In your situation it might be better to setup a subversion server rather
> than accessing the repository via the file:// url.
>
> Svnserve or Apache are relatively easy to install and configure. We use
> svnserve as a windows service on a windows server 2003 box. We've never
> had any problems with it.
>
> I know this doesn't answer your question but it does provide an
> alternative ;-)
> _________________________________________________________________
> Keith Moore
>
> -----Original Message-----
> From: NElizaga [mailto:ne_at_planitagency.com]
> Sent: Thursday, 22 May 2008 10:29
> To: users_at_subversion.tigris.org
> Subject: "can't get exclusive lock" error when attempting commit
>
>
> Hi! I'm an SVN beginner, and this is my first time posting to this mailing
> list. I know there's been tons of threads regarding the "can't get
> exclusive
> lock" error, but my situation is slightly different and I was curious if
> there was any way to solve it.
>
> We are mainly PC based, and our best machine for running the svn server
> (hard drive space and reliability) is a Windows Server 2003 machine. I set
> it up on that and have been using SVN without any errors, until I tried to
> work on and commit from one of our Macs. When using SVN from the PC I
> access
> the server using file:///newdev/SVN, but on the Mac I have to use
> file:///Volumes/newdev/SVN (mounting the network drive). I don't really
> understand why I don't get any errors on the PC but all of a sudden the
> Mac
> tries to do something that throws that error. I can check out files
> perfectly fine on the Mac, but as soon as I try and commit I get the
> infamous "can't get eclusive lock" message.
>
> I'm obviously no expert on the matter, so if I'm doing something wrong
> please call me out on it ;) I'd love to get this solved without having to
> buy new hardware or move too much stuff around, so any
> feedback/suggestions
> would be appreciated. Thanks!
>
> -Nicolas
> --
> View this message in context:
> http://www.nabble.com/%22can%27t-get-exclusive-lock%22-error-when-attempting-commit-tp17395050p17395050.html
> Sent from the Subversion Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
> #####################################################################################
> Attention:
> The information contained in this message and or attachments is intended
> only for the person or entity to which it is addressed and may contain
> confidential and/or privileged material. Any review, retransmission,
> dissemination or other use of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient
> is prohibited. If you received this in error, please contact the sender
> and
> delete the material from any system and destroy any copies.
> #####################################################################################
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
>

--
View this message in context: http://www.nabble.com/%22can%27t-get-exclusive-lock%22-error-when-attempting-commit-tp17395050p17395589.html
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
#####################################################################################
Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender and
delete the material from any system and destroy any copies.
#####################################################################################
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org