X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 521CF9DC81E for ; Wed, 14 Dec 2005 11:49:25 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87119-06 for ; Wed, 14 Dec 2005 11:49:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.kivi.com.tr (mail.kivi.com.tr [213.143.254.37]) by postgresql.org (Postfix) with ESMTP id 0592A9DC887 for ; Wed, 14 Dec 2005 11:49:19 -0400 (AST) Received: from pgbuildfarm.gunduz.org (unknown [212.174.30.202]) by mail.kivi.com.tr (Postfix) with ESMTP id DB3B18000F; Wed, 14 Dec 2005 17:49:05 +0200 (EET) Subject: Re: PG 8.1.1 rhel-as-4 rpms missing - Now not initdb issues From: Devrim GUNDUZ To: Tom Lane Cc: Chris Hoover , "pgsql-admin@postgresql.org" In-Reply-To: <19703.1134574925@sss.pgh.pa.us> References: <1d219a6f0512131059lec41586kb3b726ce2439be70@mail.gmail.com> <1134559169.19894.1.camel@devrim.kivi.com.tr> <1d219a6f0512140643w3bb51784t9956df689fb8222c@mail.gmail.com> <19703.1134574925@sss.pgh.pa.us> Content-Type: text/plain Organization: Command Prompt Inc. Date: Wed, 14 Dec 2005 17:54:53 +0200 Message-Id: <1134575693.2465.1.camel@devrim.kivi.com.tr> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-Kivi-MailScanner-Information: Please contact the ISP for more information X-Kivi-MailScanner: Found to be clean X-Kivi-MailScanner-SpamCheck: not spam, SpamAssassin (score=1.842, required 6, autolearn=disabled, FORGED_RCVD_HELO 0.05, RCVD_IN_NJABL_DUL 1.66, RCVD_IN_SORBS_DUL 0.14) X-Kivi-MailScanner-SpamScore: 1 X-Kivi-MailScanner-From: devrim@commandprompt.com X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.03 required=5 tests=[AWL=0.030] X-Spam-Score: 0.03 X-Spam-Level: X-Archive-Number: 200512/125 X-Sequence-Number: 19845 Hi, On Wed, 2005-12-14 at 10:42 -0500, Tom Lane wrote: > > Hmm. Two questions: > > - Is SELinux enabled? > > I think that's the only question you need ;-). And the answer is > probably "get a newer version of selinux-policy". Disallowing the > postgres executable from writing on /dev/tty was one of the earlier > policy mistakes ... I'm pleased to always disable SELinux :) . I remember to have an OpenWebmail problem months ago that drove me crazy, and at last I found that it was a SELinux problem. Regards, -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/