Re: Installation layout is still hazardous for shared prefixes - Mailing list pgsql-hackers

From Jim Mercer
Subject Re: Installation layout is still hazardous for shared prefixes
Date
Msg-id 20000927110206.C22260@reptiles.org
Whole thread Raw
In response to Re: Installation layout is still hazardous for shared prefixes  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 27, 2000 at 10:53:43AM -0400, Tom Lane wrote:
> I think it would be a real bad idea to put the postmaster and postgres
> executables right in /usr/local/bin.  Perhaps it is time to think about
> a separate 'sbin' directory for programs that aren't supposed to be
> invoked by normal users.  Those two, initdb, initlocation, and ipcclean
> could certainly go to sbin, also pg_id, maybe the create/drop scripts
> if you feel those are admin-only.  Perhaps using a private sbin directory
> could eliminate the issue of needing to rename stuff.

generally there is a /usr/local/sbin or /usr/local/libexec for things like
postgres and postmaster.

at least on freebsd.

if we are gonna go this route, i  would prefer that we not have any "special"
directories for postgres, other than the data directory.

a layout of:

/usr/local/bin
/usr/local/include/pgsql
/usr/local/lib
/usr/local/libexec
/usr/local/pgsql/data or /usr/local/pgsql

the last one could also be /home/pgsql or whatever.

-- 
[ Jim Mercer                 jim@reptiles.org              +1 416 410-5633 ]
[          Reptilian Research -- Longer Life through Colder Blood          ]
[  Don't be fooled by cheap Finnish imitations; BSD is the One True Code.  ]


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Installation layout is still hazardous for shared prefixes
Next
From: The Hermit Hacker
Date:
Subject: Recovery from hard drive failure ... the hard way ...