pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <jnasby@pervasive.com>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: zhuge xiao <zhuge@Rinaix.cn>
Cc: pgsql-admin@postgresql.org
Subject: Re: Help Me !
Date: Wed, 21 Dec 2005 15:25:25 -0600
Message-ID: <20051221212525.GH72143@pervasive.com> (raw)
In-Reply-To: <1135195878.18741.28.camel@state.g2switchworks.com>
References: <43A7D28C.8040504@Rinaix.cn>
	<20051221200258.GF72143@pervasive.com>
	<1135195878.18741.28.camel@state.g2switchworks.com>

On Wed, Dec 21, 2005 at 02:11:18PM -0600, Scott Marlowe wrote:
> On Wed, 2005-12-21 at 14:02, Jim C. Nasby wrote:
> > On Tue, Dec 20, 2005 at 05:44:44PM +0800, zhuge xiao wrote:
> > > Is the server running locally and accepting connections on Unix domain 
> > > socket "/tmp/.s.PGSQL.5432"?
> > 
> > So what are the permissions on /tmp/.s.PGSQL.5432? Can apache write to
> > it?
> > 
> > Actually, I think apache normally chroot's to ServerRoot (httpd.conf)
> > when it starts. So you probably need to create a symlink from
> > /tmp/.s.PGSQL.5432 to "ServerRoot"/tmp.
> 
> My apache doesn't do this, and it's a pretty straight forward source
> compile of whatever the latest version of the 2.x branch was late this
> last summer.

A coworker just confirmed that it in fact does not chroot by default.
Which had I thought about it for 1/2 a second makes perfect sense,
otherwise it would often have a heck of a time getting to
/home/*/public_html.

> However, I could see SELinux getting in the way.

Definately.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461



view thread (19+ messages)

Message-ID: <20051221212525.GH72143@pervasive.com>
Permalink:  ../20051221212525.GH72143@pervasive.com/
Also on:    postgresql.org/message-id/20051221212525.GH72143@pervasive.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, smarlowe@g2switchworks.com, zhuge@Rinaix.cn
  Subject: Re: Help Me !
  In-Reply-To: <20051221212525.GH72143@pervasive.com>
  References: <43A7D28C.8040504@Rinaix.cn> <20051221200258.GF72143@pervasive.com> <1135195878.18741.28.camel@state.g2switchworks.com> <20051221212525.GH72143@pervasive.com>

* 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