Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Updated macOS start scripts
From: Mark Dilger <hornschnorter@gmail.com>
In-Reply-To: <31338.1510763554@sss.pgh.pa.us>
Date: Wed, 15 Nov 2017 10:13:21 -0800
Cc: pgsql-hackers@postgreSQL.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D443E39-13C2-4185-9FE4-B5CB416AB06E@gmail.com>
References: <31338.1510763554@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Precedence: bulk


> On Nov 15, 2017, at 8:32 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> The stuff in contrib/start-scripts/osx/ does not, as far as I know,
> work at all on any recent release of macOS, because SystemStarter
> is long gone.  I propose replacing it with the attached, which
> I've tested on current-vintage Macs.
>=20

I tested the presence of SystemStarter, which the old implementation
uses, and launchd and launchctl, which your new implementation uses,
on a couple of my mac laptops:

	OS X 10.11.6
		SystemStarter  - not installed
		launchd - installed
		launchctl - installed

	OS X 10.6.8
		SystemStarter - installed
		launchd - installed
		launchctl - installed

According to Wikipedia:

"SystemStarter appears to have been removed from OS X 10.10 and later =
(reference needed)."

and

"In Mac OS X v10.4, it was deprecated in favor of launchd"

Overall, I think supporting 10.10 and greater is more relevant than =
continuing
to support 10.4 and earlier, though I suppose someone could argue for
keeping both in side-by-side files with the README directing users which =
to
use for whichever version of OS X they happen to be running.  It's of no
consequence to me, since my oldest mac is running 10.6.8, but somebody
from the museum of old macs might feel differently.

mark