Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Francisco Olarte <folarte(at)peoplecall(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Stephens, Gary" <Gary(dot)Stephens(at)ehi(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"
Date: 2023-03-08 15:50:23
Message-ID: 190974.1678290623@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Francisco Olarte <folarte(at)peoplecall(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2023-03-08 16:22:07 Re: BUG #17824: PQTRANS_ACTIVE misleading
Previous Message Thomas Munro 2023-03-08 11:57:20 Re: BUG #17368: Assert failed in GetSafeSnapshot() for SERIALIZABLE READ ONLY DEFERRABLE transaction