From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff - <threshar@torgo.978.org>
Cc: pgsql-docs@postgresql.org
Subject: Re: SELinux & Redhat
Date: Fri, 06 May 2005 11:57:47 -0400
Message-ID: <15121.1115395067@sss.pgh.pa.us> (raw)
In-Reply-To: <6CD32D5F-B466-4E6D-9E73-CFB8957B396F@torgo.978.org>
References: <BCAFEEBE-43EC-446F-95CF-A920CD43FE36@torgo.978.org>
<14695.1115393034@sss.pgh.pa.us>
<6CD32D5F-B466-4E6D-9E73-CFB8957B396F@torgo.978.org>
Jeff - <threshar@torgo.978.org> writes:
> When I run pg_dump w/these settings the following happens running
> pg_dump (.broken is hte original file from the rpm)
> bash-3.00$ /usr/bin/pg_dump.broken planet
> bash-3.00$
Does it work if you direct the output into a file, instead of letting it
come to your terminal (which seems a bit useless anyway)?
I've been bugging dwalsh about the fact that the selinux policy
disallows writes to /dev/tty to things it thinks are daemons;
that seems pretty stupid. But pg_dump isn't a daemon so there's
no reason for it to be restricted this way anyway...
> and what is interesting is it seems only sometimes things get logged
> to syslog about the failure.
Someone told me there's a rate limit on selinux complaints going to
syslog, to keep it from swamping your logs. I suspect there are some
actual bugs there too, because I've noticed cases where an action was
blocked and there wasn't any log message, nor enough activity to
justify a rate limit. Feel free to file a bugzilla report if you can
get a reproducible case.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, threshar@torgo.978.org, pgsql-docs@postgresql.org
Subject: Re: SELinux & Redhat
In-Reply-To: <15121.1115395067@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox