Public bug reported: Binary package hint: postgresql-common
Hardy, postgresql-common 86 This bug was discovered when encountering Bug #203920, where the postgres database does not start. That test suggests determining the status of the database by "sudo -u postgres psql -l". Alternatively, one should also be able to use: "/etc/init.d/postgresql-8.3 status". However, that action actually lists the postgres clusters and looks for one that is marked "down". In this case, the local daemon is dead and we have no clusters. The Linux Standard Base specification defines the expected responses and return codes of init script status actions: http://refspecs.freestandards.org/LSB_3.2.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html According to that document, I think the proper approach would be to exit with "4 program or service status is unknown" if there are no clusters found. ** Affects: postgresql-common (Ubuntu) Importance: Undecided Status: New -- init script status action does not reflect dead postgresql service https://bugs.launchpad.net/bugs/203966 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
