SysV status script returns the wrong exit code when postgresql is not running
Bug #921001 reported by
Glenn Aaldering
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postgresql-common (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
SysV status script returns the wrong exit code when postgresql is not running:
[Precise]
# /etc/init.
Running clusters:
# echo $?
0
This seems to work ok in Lucid:
[Lucid]
# /etc/init.
Running clusters:
# echo $?
3
affects: | postgresql-9.1 (Ubuntu) → postgresql-common (Ubuntu) |
Changed in postgresql-common (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
The attached patch fixes the exit status for me.