public inbox for [email protected]  

help / color / mirror / Atom feed

From: Devrim GUNDUZ <[email protected]>
To: Tom Lane <[email protected]>
Cc: Jeff - <[email protected]>
Cc: [email protected]
Subject: Re: SELinux & Redhat
Date: Fri, 6 May 2005 18:33:20 +0300 (EEST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi,

On Fri, 6 May 2005, Tom Lane wrote:

> Jeff - <[email protected]> writes:
>> Eventually we found it was SELinux was preventing pg_dump from
>> producing output.
>
> That's a new one on me.  Why was it doing that --- mislabeling on
> the pg_dump executable, or what?

Looking at the strace report that someone has sent me before, there is a 
problem with devices:

===================================================================
<snip>
fstat64(1, {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 3), ...}) = 0
ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe16a8c) = -1 ENOTTY
(Inappropriate ioctl for device)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7dee000
write(1, "pg_dump dumps a database as a te"..., 2367) = 2367
munmap(0xb7dee000, 4096)                = 0
exit_group(0)                           = ?
===================================================================

This one is from a server with SELinux enabled. My server does not produce 
this, and uses virtual console (as expected?). However with SELinux 
enabled, it wants to use ramdisk (expected? I think no...)

Regards,
- --
Devrim GUNDUZ 
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com.tr                      http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCe45Btl86P3SPfQ4RAhpbAJ0UhBh8dlOEpPsNm2NB1QIJ82X2swCg7JOg
A1OCBrZRHxoOPQo0U9hNdNY=
=ENTC
-----END PGP SIGNATURE-----

view thread (24+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: SELinux & Redhat
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox