Thanks Yes, I’m aware of that problem. Got caught the same way. However … after an update, I just check that the plist file hasn’t been modified, and so far so good. I don’t know why it isn’t, but maybe someone at Apple has decided that they can leave some things alone.
Initially it was a problem, but not the last two times. But I still check. I haven’t installed the Server software. No need for it in my case. I’d rather roll my own :-) > On 3 Jan 2017, at 16:15, Jim Reid <j...@rfc1035.com> wrote: > > >> On 3 Jan 2017, at 14:37, Robert Chalmers <racu...@icloud.com> wrote: >> >> To start Postscript I use the following plist file. Based in >> /Library/LaunchDaemons >> >> org.postfix.master.plist > > Don’t do that. Pick names for your own plist files that don’t clash with the > ones Apple use. There will be confusion if your plist files (in > /Library/LaunchDaemons or wherever) have the same names as those in > /System/Library/LaunchDaemons. For example, you think you’re running your own > instance of postfix when the OS is actually running Apple’s. Or vice versa. > Or both end up running and launchd eventually kills one of them since it’s > had to restart that daemon too often because the daemon’s unable to listen on > a port already used by the other instance. > > It gets even worse if you install Apple Server software. That includes a > script (cron job?) which secretly tells launchd to unload things like > whatever bind and postfix is running and replace them with the > Server-flavoured versions which are controlled from > /Applications/Server.app/Contents/ServerRoot/System/Library/LaunchDaemons. > > I found this out the hard way. >
