Re: Re: Sure enough, the lock file is gone

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: Sure enough, the lock file is gone
Date: 2001-01-29 05:57:02
Message-ID: 200101290557.AAA12120@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian wrote:
> > No one has suggested a location non-root people can put the socket/lock
> > file, except /tmp, and IMHO, until we find one, the default stays in
> > /tmp.
>
> Since RPM's _must_ be installed by root, that doesn't affect them. The
> debian packages are the same way. As long as the RPM contains the
> structures set as owned by 'postgres' (the default run user for
> postmaster), and the appropriate permissions are set, the directory
> could be anywhere, such as /var/run/pgsql. But there are of course
> problems with that approach, because libpq makes some hard-coded
> assumptions about where to look.

The issue we have is that we don't assume root installs. Any root
requirement is going to be RPM-specific.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oliver Elphick 2001-01-29 06:29:17 Re: Re: Sure enough, the lock file is gone
Previous Message Lamar Owen 2001-01-29 04:44:50 Re: Re: Sure enough, the lock file is gone