How to lock the SVN repository?

This is using the SVN (subversion) to control the version number of the code. The source server is an VM using CentOS 6.4, while the destination server is a redhat Enterprise linux 6.7. Both Linux systems are installing SVN by yum, for example, yum install subversion, and yum install mod_dav_svn. apache (httpd) was utilized. The version of SVN is 1.6.

As for the SVN structure, the httpd.conf located in /etc/httpd, while all SVN repository config are put in /etc/httpd/conf.d. However, all SVN repository are stored in /home/svn. As for the user authentication, LDAP is in used, in which this pointed to our MS Windows AD Domain. Both systems were setup in the same fashion.

Now, selective repositories are needed to be migrated from CentOS to redhat linux. The redhat linux SVN server is working now. However, as for the old centOS svn server, those affected repository still kept but none of them should allow committed or updated.
Is there a way to "lock" all the files and folders of those affected repository, sounds like using "svn lock" or else? Or only allow those users to read-only but not write?

Please help, thanks a lot.
MichaelBalackSenior System EngineerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

From the new svn server, checkout the data you copy into the new repository.
Change permission on the repository removing write rights.
MichaelBalackSenior System EngineerAuthor Commented:
Hi Arnold,

How to "Change permission on the repository removing write rights"?

Are you referring to linux file permissions? by default each repo is assigned 755, so change this to 311? or else?
Yes, changing the
555 removes write access on directories, 444 on files.
But before check the svn checkout status to make sure that if someone is still working on changes, that they commit the changes they .......

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MichaelBalackSenior System EngineerAuthor Commented:
Thanks for Expert Arnold in suggesting the remove WRITE permissions. It works.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.