From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8F2F3138359 for ; Mon, 5 Oct 2020 14:52:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 122DEE0930; Mon, 5 Oct 2020 14:52:02 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C9C90E0922 for ; Mon, 5 Oct 2020 14:52:01 +0000 (UTC) Received: by martineau.localdomain (Postfix, from userid 1000) id 84D821C55228C; Mon, 5 Oct 2020 10:51:57 -0400 (EDT) Date: Mon, 5 Oct 2020 10:51:57 -0400 From: "Aaron W. Swenson" To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] New acct-user/pgbouncer Message-ID: <20201005145157.GA20055@martineau.home.grandmasfridge.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline X-Archives-Salt: 9d04149b-7d2b-4588-bbe8-0849782e9262 X-Archives-Hash: 5d81937d7b296f75e6e3e9b9a26b0acd --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Currently we're just using -1 for pgbouncer. The user does own a couple things, but that's managed by checkpath in the init script. So, given that any UID will do, I'm proposing either 383 (I think someone else is asking for 384) or 463. Pgbouncer only needs a UID. It uses the postgres GID. Which UID should we use: 383 or 463? --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQE1BAAWCgDdFiEEBAujrfkChUViF3zk/5dcDSiUpdEFAl97Mw1fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDA0 MEJBM0FERjkwMjg1NDU2MjE3N0NFNEZGOTc1QzBEMjg5NEE1RDFfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDA0 MEJBM0FERjkwMjg1NDU2MjE3N0NFNEZGOTc1QzBEMjg5NEE1RDEACgkQ/5dcDSiU pdFDVAD+NFGlXgeVWyI0JgBJXcebIyEHNJbcvBAMdZWcvlzcZTEA/iPuJ/Rz+jEH k4rdgfnbAMuRa86ZnSJOqq8ANdBEw7gL =zDeU -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--