Analysis and Handling of rsync restart Problems

On July 15, May, the channel summary statistics failed. The cause was found: 81.180 machine pulled the newGarden.2010-05-13 file on 205.80 machine, and the execution failed, the error "data2 unknown module information" is reported ". The 31.21 server pulls the newGarden.2010-05-13 file from the 205.80 server, and the file is successfully pulled. Check the hostsallow list and module configuration information. Then, restart the rsync process on the machine 205.80, and the two machines can smoothly pull the files on the machine 205.80.

Rsync restart analysis:

After reading the machine initialization script, the script adds a [data2] module configuration to the rsyncd. conf file. But the rsync process was not restarted, So I suspected it was a problem. So I went to the Internet to check whether the rsync configuration file needs to be restarted after modification.

There is an article on the Internet about whether to restart the rsync configuration after modification:

[1. during use, it is found that you need to restart the rsync process to modify the global configuration (the global variable in the configuration file). When you modify the attribute configuration of a specified Modual, then it takes effect immediately without restarting the rsync process. When a variable name exists in both global and local variables, the value of the local variable overwrites the value of the global variable for this module.

2. for the above conclusion, the hostsallow variable should be noted in the difference between hostallow during use: Once a colleague hosts wrote the host, and I haven't figured out why after a long time, I thought it was necessary to restart the system to take effect. In fact, rsync did not recognize "hostallow" at all, but no error was reported. Therefore, you should pay attention to some syntactic errors during configuration modification.

3. -- delete option, the directories on both sides cannot end with/*, because shell will extend * to all files under this Directory]
After an experiment, the content above is true.

However, this theory cannot explain the problems above. Later, I checked the rsync manual and didn't talk about whether to restart the rsync configuration file after modification. In this case, it is better to restart the process after modifying the rsyncd. conf file in the initialization script of the statistical machine.

So why does rsync restart?

First, determine whether the rsync process exists:
Psauxf | grep 'rsync'
In this way, you can see the rsync process startup method.
Root234190.0041514344764? Ss20090: 34/usr/bin/rsync -- address = 172. **. **. *** -- daemon

2. rsync Restart Method: kill the process first and then start the process.
Restart the process and use the statements observed above.

Further, you may use the above method when you do not know how to start the program and do not want to find the Startup File.