since launchd is now the preferred way of launch system services it would be good if radmind could take the socket in a graceful way from the launchd process. I had a launchd.plist that would not work for some reason. Finally found this reference
It seems that there is some internal magic in that launchd will attach to the port and then pass it on to the program. If you have a "Sockets" section in the XML file radmind will fail telling you that the port is busy and it cannot bind.
If you delete the "sockets" section of the launchd.plist it will work but then you are hiding from launchd the resources it is trying to keep track of. I think it needs to do a checkin with launchd
Log in to post a comment.