| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David(dot)I(dot)Noel(at)gmail(dot)com |
| Cc: | Amitabh Kant <amitabhkant(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, PGSQL Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: initdb error |
| Date: | 2012-12-15 16:28:44 |
| Message-ID: | 24277.1355588924@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
David Noel <david(dot)i(dot)noel(at)gmail(dot)com> writes:
> Ugh. It turns out I had security.bsd.hardlink_check_gid=1 and
> security.bsd.hardlink_check_uid=1 in sysctl.conf. Setting them to 0
> fixed everything. That's frustrating. Sorry for all the trouble. Many
> thanks for helping resolve this.
Hah, I wondered if it might be something like that. Still, it's hard to
see how this link() would fail any security check that didn't amount to
disabling link() altogether. The UID and GID of the process, the old
file, and the directory will all match --- so exactly what rule are we
falling foul of? (Or IOW, this still seems like a kernel bug, though
perhaps of a design rather than implementation kind.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-12-15 17:29:20 | Re: initdb error |
| Previous Message | David Noel | 2012-12-15 15:10:27 | Re: initdb error |