This was fixed in version 135, and thus in raring. ** Package changed: postgresql-9.1 (Ubuntu) => postgresql-common (Ubuntu)
** Bug watch added: Debian Bug tracker #656363 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656363 ** Also affects: postgresql-common (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656363 Importance: Unknown Status: Unknown ** Changed in: postgresql-common (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-common in Ubuntu. https://bugs.launchpad.net/bugs/1076860 Title: PostgreSQL init script wrongly returns 0 for "status" when no clusters are running Status in “postgresql-common” package in Ubuntu: Fix Released Status in “postgresql-common” package in Debian: Unknown Bug description: Because "set +e" is set in the "status" case of the postgresql init script, running "service postgresql status" or "/etc/init.d/postgresql status" always returns with exit code 0. Even when no clusters are running the exit code is 0, when it should really be 3, indicating that the service is not running (as per LSB specs). This has negative implications for Pacemaker, Puppet and other applications that expect init scripts to conform to LSB specifications. Attached is a simple patch that removes "set +e" and makes the init script behave properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1076860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
