MacPort's rsyncd error messages after changing ssh port

[Richard L. Hamilton]

> On Feb 19, 2020, at 06:23, Ryan Schmidt <ryandesign at macports.org> wrote:
> 
> On Feb 17, 2020, at 13:32, Artemio González López wrote:
> 
>> After changing the sshd port from 22 to a non-standard (high) number, I’ve noticed that my system.log is flooded with error messages like the following, coming from MacPort’s rsync daemon:
>> 
>> Feb 17 20:11:05 my-compuer-name com.apple.xpc.launchd[1] (org.macports.rsyncd[18457]): Service exited with abnormal code: 2
>> 
>> I tried to debug this problem executing "sudo launchctl debug system/org.macports.rsync --stdout —stderr” and got the following error message (which I don’t understand):
>> 
>> Configuration failed: 113: Could not find specified service
>> Could not find service "org.macports.rsync" in domain for system
>> 
>> rsync and port selfupdate work well, but as I said this is quickly filling up my log (at the rate of one message every 30 seconds or so). Could anybody tell me what’s causing this, and how to fix it?
> 
> I guess at some point you ran "sudo port load rsync" to tell MacPorts to tell launchd to run the rsync program as a server and keep it running, in order to host your own rsync server. I guess something about that isn't set it up correctly, so it can't start, and it exits with an error; launchd is then doing what you told it to do and starting rsync again, which exits again, etc. You can use "sudo port unload rsync" to tell MacPorts to tell launchd to stop trying to keep rsync running, and then you won't be trying to run your own rsync server anymore. This will have no effect on your ability to use the rsync program as a client to talk to some other rsync server, for example when you use "sudo port selfupdate".
> 
> If you really do want to run rsync as a server and can't figure out why it's not working, let us know; I won't be able to help you but maybe someone else will.
> 
> 


On I think more than one occasion, I've had issues with the MacPorts LaunchDaemon plist files that use "daemondo". When something can be done that doesn't need that to reconcile the differences between traditional daemons and what launchd expects, that's worked better for me. I made my own local.rsyncd.plist  and used that instead:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Disabled</key>
	<true/>
	<key>Label</key>
	<string>local.rsyncd</string>
        <key>Program</key>
        <string>/opt/local/bin/rsync</string>
        <key>ProgramArguments</key>
        <array>
                <string>/opt/local/bin/rsync</string>
                <string>--daemon</string>
        </array>
        <key>inetdCompatibility</key>
        <dict>
                <key>Wait</key>
                <false/>
        </dict>
		<key>Sockets</key>
		<dict>
			<key>Listeners</key>
			<dict>
				<key>SockServiceName</key>
				<string>rsync</string>
				<key>SockType</key>
				<string>stream</string>
			</dict>
		</dict>
</dict>
</plist>