Solve the SVN startup problem in CentOS6.5

Recently, due to the business needs of the company, I have migrated the svn of the current development project to the ECS (not installed by the author) one day after I restarted the server, I found that the SVN connection failed (see ). Run svnserver-d-r/home/lyh/svn/store. Last

Recently, due to the business needs of the company, I have migrated the svn of the current development project to the ECS (not installed by the author) one day after I restarted the server, I found that the SVN connection failed (see ). Run svnserver-d-r/home/lyh/svn/store.

 

Finally, no IP address is set for the listener. the following command sets the IP address of the listener:

 

[Plain]View plaincopyprint?

1. Svnserve-d-r/home/svn/repos -- listen-host 123. **. 120 .**

 

In this case, SVN is successfully started.

 

During this process, the following message will be prompted if you start the system incorrectly and then start it with the correct command.

 

In this case, you must first start the command

 

[Plain]View plaincopyprint?

1. Ps-ef | grepsvnserve

 

View the running svn process and then use the command

 

[Plain]View plaincopyprint?

1. Kill-9 2235 (killing 2235 processes)

 

Finally, use the correct command.

 

Later, I thought this was actually quite troublesome. Although the server was not often restarted, it was quite troublesome to configure this configuration every time I restarted it. Finally, I wrote a script and it would be okay to start it directly every time I started it.

Set startup

1. create the execution script svn. sh (/root path). The content is as follows:

 

[Plain]View plaincopyprint?

1. #! /Bin/bash
2. Svnserve-d-r/home/svnroot/repository

 

2. add execution permission

 

[Plain]View plaincopyprint?

1. # Chmod ug + x/root/svn. sh

 

3. add automatic run

 

[Plain]View plaincopyprint?

1. # Vi/etc/init. d/rc. d/rc. local

Add/root/svn. sh to it

 

4. save and exit

Press Esc on the disk and then ": wq" to save the file and exit vi.

Finally, restart and try it on our own, so that we can use it once and for all. the first few lines of commands may make us less trouble in the future.