Activity log for bug #248939

Date Who What changed Old value New value Message
2008-07-16 08:54:24 Florian Hackenberger bug added bug
2008-09-04 12:28:32 Mathias Andre bug added attachment 'diff.postgresql' (diff.postgresql)
2008-09-04 12:29:14 Mathias Andre bug added subscriber Dustin Kirkland
2008-09-20 20:14:40 Martin Pitt postgresql-8.3: status New Incomplete
2008-09-20 20:14:40 Martin Pitt postgresql-8.3: bugtargetdisplayname postgresql-8.3 (Ubuntu) postgresql-common (Ubuntu)
2008-09-20 20:14:40 Martin Pitt postgresql-8.3: bugtargetname postgresql-8.3 (Ubuntu) postgresql-common (Ubuntu)
2008-09-20 20:14:40 Martin Pitt postgresql-8.3: statusexplanation I don't understand what's wrong with the current init script. The "status" action already behaves LSB like, exiting with 0 if everything is running, with 3 if a cluster is down, and with 4 if no clusters are existing. Since the script is set -e, the "exit $?" patch is a no-op and does not change anything. What would status_of_proc change here? IMHO using pg_lsclusters and pg_ctl are slightly more accurate here. In either case, this should be changed in /usr/share/postgresql-common/init.d-functions and thus in postgresql-common, reassigning.
2008-09-20 20:14:40 Martin Pitt postgresql-8.3: title Bug #248939 in postgresql-8.3 (Ubuntu): "postgre init script is not LSB compliant (for heartbeat, i.e. linux-ha)" Bug #248939 in postgresql-common (Ubuntu): "postgre init script is not LSB compliant (for heartbeat, i.e. linux-ha)"
2009-02-15 15:18:56 Martin Pitt postgresql-common: status Incomplete Invalid
2009-02-15 15:18:56 Martin Pitt postgresql-common: statusexplanation I don't understand what's wrong with the current init script. The "status" action already behaves LSB like, exiting with 0 if everything is running, with 3 if a cluster is down, and with 4 if no clusters are existing. Since the script is set -e, the "exit $?" patch is a no-op and does not change anything. What would status_of_proc change here? IMHO using pg_lsclusters and pg_ctl are slightly more accurate here. In either case, this should be changed in /usr/share/postgresql-common/init.d-functions and thus in postgresql-common, reassigning. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
2009-06-09 14:57:02 Martin Pitt postgresql-8.3 (Ubuntu): status New Invalid