Bug 91943 - Postgresql init script system boot failure
Summary: Postgresql init script system boot failure
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: postgresql
Version: 9
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Fernando Nasser
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
: 97605 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-30 04:56 UTC by Cristian Gafton
Modified: 2007-04-18 16:54 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2003-06-18 11:53:54 UTC


Attachments (Terms of Use)

Description Cristian Gafton 2003-05-30 04:56:18 UTC
The postgresql init script is trying to figure out how it is called as and
therefore at the startup does somethin like:
NAME=`basename $0`

Based on that $NAME then it tries to read the /etc/sysconfig/pgsql/$NAME
configuration file, if it exists.

There are 2 problems that keep this from working right:
- first, during the system bootup time, the script is called as S85postgresql,
which means that $NAME is assigned 'S85postgresql' instead of the desired
'postgresql'. This works correctly when doing a "system postgresql restart", but
fails to read the postgresql config file during the first boot.

- secoindly, in the config file one could define the PGOPTS variable with
additional options to be passed to the postgres engine by the postmaster daemon.
While that variable is exported from the init script, it is used nowhere in the
start() function, therefore rendering it useless.

Comment 1 Andrew Overholt 2003-05-30 18:34:05 UTC
The init script is currently in the process of being overhauled.  I've never
really seen the point of the basename ilne anyways, but that is an easy fix. 
Usage of PGOPTS can be integrated with the coming enhancements.  Re-assigning to
fnasser who is working on the init script.

Comment 2 Andrew Overholt 2003-06-18 11:53:54 UTC
These two issues are fixed in RAWHIDE.

Comment 3 Andrew Overholt 2003-06-18 11:54:38 UTC
*** Bug 97605 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.