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-directory
(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.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
