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. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
