From: | Gerd Koenig <koenig(at)transporeon(dot)com> |
---|---|
To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: problem with pg_standby |
Date: | 2010-08-04 06:49:30 |
Message-ID: | 201008040849.30871.koenig@transporeon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
thanks Greg,
yes, we want SELinux in enforcing mode.
Thereby (and to ensure persistence) just chcon is the wrong way and
* semanage fcontext -a -t postgresql_t '<dir>'
* restorecon -vvFR <dir>
is much better ;-)
regards--GERD--
On Wednesday, August 04, 2010 07:56:56 am Greg Smith wrote:
> Gerd Koenig wrote:
> > thanks for the hint, yes, SELinux caused the troubles. It complained
> > about wrong filecontext while starting postgres via init-script.
> >
> > Filecontext was: var_lib_t and it should be: postgresql_t
>
> If you want to keep SELinux on, basically you have to relabel the
> directory you are putting those into so it can access them. You might
> find some useful hints on that topic at
> http://serverfault.com/questions/32333/how-does-selinux-affect-the-home-dir
> ectory (including the observation that /home is a bad place for them). You
> might think you can just run the chcon command to reset the labels, but it
> doesn't quite work like that; you have to change the policy and then use
> restorecon to correct them.
From | Date | Subject | |
---|---|---|---|
Next Message | David R Robison | 2010-08-04 11:21:02 | Re: PG 8.4 won't start on Windows Server 2008 64-bit |
Previous Message | Greg Smith | 2010-08-04 05:56:56 | Re: problem with pg_standby |