Tom Lane wrote:
> Christine Desmuke <cdesmuke@kshs.org> writes:
>> Tom Lane wrote:
>>> Years ago I saw roughly similar symptoms when SELinux decided postgres
>>> shouldn't be allowed to write to /dev/tty.
>
>> Thanks for the suggestion. It is not SELinux (SELinux status:
disabled), but _something_ is preventing postgres (both the existing
install and the one I'm trying to check) from writing to /dev/tty.
>
> You *sure* selinux is disabled? Because that sounds exactly like a
> long-ago selinux policy bug. I'd have thought everybody's machine
> had the fix by now, but if this machine isn't too up2date, maybe not...
>
> regards, tom lane
[root@zu ~]# sestatus
SELinux status: disabled
[root@zu ~]# more /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted
[root@zu ~]# uname -r
2.6.9-78.0.22.ELsmp
Yes, the symptoms look like an selinux problem, except the machine
claims selinux is disabled, and there is nothing in the logs from avc
(or anything else notable). I've updated to the latest version of CentOS
4, which is supposed to mirror RHEL 4. I'm probably missing something
obvious, but I dunno what.
Thank you, as always, for taking the time to help.
--
Christine Desmuke
Kansas State Historical Society
cdesmuke@kshs.org
