From: Tom Lane <tgl@sss.pgh.pa.us>
To: Francisco Olarte <folarte@peoplecall.com>
Cc: David G. Johnston <david.g.johnston@gmail.com>
Cc: Stephens, Gary <Gary.Stephens@ehi.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
Date: Wed, 08 Mar 2023 10:50:23 -0500
Message-ID: <190974.1678290623@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+bJJbzuJPqGgYwrLeVKJh6GgPUSB6XdD38yLmFcdEpNM-zq_A@mail.gmail.com>
References: <DM4PR11MB5328327445FFA1FE28426198F0B79@DM4PR11MB5328.namprd11.prod.outlook.com>
<CAKFQuwY495XmkvwUH_-pNp=-HdwO3yhFjGZYD7nLYWWxbmqAQw@mail.gmail.com>
<CA+bJJbzuJPqGgYwrLeVKJh6GgPUSB6XdD38yLmFcdEpNM-zq_A@mail.gmail.com>
Francisco Olarte <folarte@peoplecall.com> writes:
> Besides locking I've encountered this kind of problems with people
> having a habit of editing non-root-owned config files as root with
> editors which do not take care of setting permissions. An ls -l of the
> offending file is normally useful, or the version with all extended
> acl/attrs which I'm unable to recall now.
Yeah, "ls -lZ" to see SELinux labels. It's easy to forget about those
if you're not pretty used to them.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, folarte@peoplecall.com, david.g.johnston@gmail.com, Gary.Stephens@ehi.com, pgsql-bugs@lists.postgresql.org
Subject: Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
In-Reply-To: <190974.1678290623@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox