The official guide helped me figure out some of the specifics of setting up
the server, and more importantly showed me how to type out the svn path. So,
using the svn:// I no longer get those errors! Thanks for your help,
everyone!
-Nick
John Peacock-4 wrote:
>
> NElizaga wrote:
>> 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?
>
> svnserve is an alternative to Apache. Both of them are server processes
> that
> exclusively access the repository files on the local drive. You should
> use one
> of them instead of accessing the repository files over the network (which
> isn't
> a good idea for exactly the reasons you've already noticed).
>
>> The path to the network drive is //newdev/SVN, so naturally I assumed it
>> would work like so: svn://newdev/SVN.
>
> I'm not going to download someone else's guide to Subversion, but the
> exact path
> to the files in the repository (through either svn:// or http://) depend
> completely on the configuration of the server process (svnserve and Apache
> respectively).
>
> You should probably read the official Subversion book:
>
> http://svnbook.red-bean.com/
>
> rather than relying on some random guy on the 'Net...
>
> John
>
> ---------------------------------------------------------------------
> 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-tp17395050p17416273.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
Received on 2008-05-23 02:08:47 CEST