SVN multi-version library configuration problems

SVN multi-version library configuration problems when I first came into contact with SVN, because I didn't know about it, and under Windows, I had been plagued by its multi-version library configuration problems for a long time, I have never found a perfect solution. I accidentally configured SVN in Linux and found that it is supported by configuring the -- config-file parameter to specify the global configuration file. Write down this article to correct the previous incorrect configuration (mainly in Windows) and share it with you. The processing in Linux and Windows is basically the same. First, let's look at the help information of svnserve in Linux: www.2cto.com [plain] [root @ localhost ~]. # Svnserve -- help usage: svnserve [-d |-I |-t |-X] [options] Valid options:-d [-- daemon]: daemon mode-I [-- inetd]: inetd mode-t [-- tunnel]: tunnel mode-X [-- listen-once]: listen-once mode (useful for debugging) -r [-- root] ARG: root of directory to serve-R [-- read-only]: force read only, overriding repository config file -- config-file ARG: read configuration from file ARG -- listen-po Rt ARG: listen port [mode: daemon, listen-once] -- listen-host ARG: listen hostname or IP address [mode: daemon, listen-once]-T [-- threads]: use threads instead of fork [mode: daemon] -- foreground: run in foreground (useful for debugging) [mode: daemon] -- log-file ARG: svnserve log file -- pid-file ARG: write server process ID to file ARG [mode: daemon, listen-once] -- tunnel-user ARG: tunnel Username (default is current uid's name) [mode: tunnel]-h [-- help]: display this help -- version: show program version information generally starts the SVN service, only specify the root directory of the SVN version library, as shown below: www.2cto.com [plain] svnserve-d-r/data/svn and then create multiple version Libraries under/data/svn: [plain] cd/data/svn svnadmin create repos1 svnadmin create repos2 and configure conf/svnserve under the version libraries such as repos1 and repos2 in sequence. conf, conf/passwd, and conf/authz files. The problem arises, because most of the time, the same user needs to use the same account and password to access different version libraries, and the permission configuration is not easy to handle, previously, the solution for others was in svnserve. when passwd and authz are specified in conf, the relative path is used to indicate the same file. This is a feasible method, but when adding a version library, you have to change the svnserve. conf file, which is inconvenient. After carefully reading the help information of svnserve, you will find a -- config-file parameter, which is used to specify svnserve. when it comes to the conf path, it is clear that you only need to specify the -- config-file parameter when starting the SVN service, all permissions are assigned by the specified svnserve. conf control, and svnserve under the conf directory of each version library. conf configuration will be ignored. [Plain] svnserve-d-r/data/svn -- config-file/data/svn/svnserve. conf www.2cto.com uses the CollabNet Subversion Server in Windows, which is the installed Service. The specified ImagePath format is: "d: \ Program Files (x86) \ CollabNet \ Subversion Server \ svnserve.exe "-- service-r" e: \ svn_repository "-- listen-port" 3690 ", the -- config-file parameter is not specified, as a result, new users who are new to SVN will be entangled in the configuration of Multi-version libraries. Now, just go to the Registry to change the ImagePath parameter of the SVN service and append the -- config-file parameter: [plain] "d: \ Program Files (x86) \ CollabNet \ Subversion Server \ svnserve.exe "-- service-r" e: \ svn_repository "-- listen-port" 3690 "-- config-file" e: \ svn_repository \ conf \ svnserve. conf "and the path used above, Please convert them into their respective paths. Author lixianlin