** Changed in: postgresql-8.3 (Ubuntu)
Status: New = Invalid
--
postgre init script is not LSB compliant (for heartbeat, i.e. linux-ha)
https://bugs.launchpad.net/bugs/248939
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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
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
Patch attached.
Mathias
** Attachment added: diff.postgresql
http://launchpadlibrarian.net/17285564/diff.postgresql
--
postgre init script is not LSB compliant (for heartbeat, i.e. linux-ha)
https://bugs.launchpad.net/bugs/248939
You received this bug notification because you are a member
I'm not sure that just returning the exit value will give you what you
expect because in other patches we have identified that more and more
init.d scripts are going to be running under a set -e environment
where a non-zero return value terminates the script, so in your
suggested patch, status
