opscode-cookbooks/rsync — pull request #11 by ftclausen (2014-04-01 04:41:57+00:00)
Title: Fixes to allow rsync daemon to be started if not up.

I noticed, on the Red Hat family OS's, that when the rsync daemon is not running then the chef-client run will fail to start it despite there being a "service [:enable, :start]" present in the server cookbook. This is because in the "status" case statement of the Red Hat init script two things are going wrong

* The daemon process is called "rsync" not "rsyncd"
* The script does not exit with a non-zero exit code if the service is not running

I have fixed this by correcting the process name and exiting with the return code of the "status" function. It seems to now start the daemon if it is found to be down. I am in the process of creating a Jira ticket on the Opscode side of things.