initscript doesn't preserve return code
Bug #1464770 reported by
Simon Déziel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nginx (Debian) |
Fix Released
|
Unknown
|
|||
nginx (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Wily |
Fix Released
|
Low
|
Unassigned |
Bug Description
Copied from the Debian bug (https:/
Many actions offered by the initscript do not preserve or give the
proper return code. One notable example is the "configtest" that always
returns 0 even when problems are detected:
echo "invalid" >> /etc/nging/
service nginx configtest
echo $?
Should return 1 but returns 0 instead.
Changed in nginx (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in nginx (Debian): | |
status: | Unknown → New |
Changed in nginx (Ubuntu Wily): | |
status: | Triaged → Fix Committed |
Changed in nginx (Debian): | |
status: | New → Fix Committed |
Changed in nginx (Debian): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The attachment "Same patch as the one attached to the Debian bug" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]