From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David Esposito" <pgsql-general(at)esposito(dot)newnetco(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Using an alternate PGDATA on RHEL4 with SELinux enabled |
Date: | 2006-07-28 14:35:23 |
Message-ID: | 21422.1154097323@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"David Esposito" <pgsql-general(at)esposito(dot)newnetco(dot)com> writes:
>> -----Original Message-----
>> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>> The default selinux policy prevents postgres from writing anywhere
>> except under /var/lib/pgsql. If you want a nondefault PGDATA location
>> then you have to tweak the policy.
> It's not that simple ... if I su to postgres, I can initdb and launch
> postmaster in any directory I wish (as long as it has rwx for the postgres
> user) ... it's only if I try to do this from the init.d start script that
> the problem occurs ...
Yes, it is that simple. Processes launched from start scripts inherit
a different (much more restrictive) selinux context than ones launched
from interactive shells.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2006-07-28 15:20:12 | Re: Database Design Theory - PostgreSQL Custom Types |
Previous Message | Tom Lane | 2006-07-28 13:29:12 | Re: What's special about 1916-10-01 02:25:20? Odd jump in internal timestamptz representation |