SysV status script returns the wrong exit code when varnish is not running
Bug #921008 reported by
Glenn Aaldering
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| varnish (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
SysV status script returns the wrong exit code when varnish is not running:
[Lucid]
# /etc/init.d/varnish status
* varnishd is not running
# echo $?
0
This seems to work properly in Precise:
[Precise]
# /etc/init.d/varnish status
* varnishd is not running
# echo $?
3
Revision history for this message
| Ruben Romero (huayra) wrote | #1 |
| Changed in varnish (Ubuntu): | |
| status: | New → Invalid |
To post a comment you must log in.
Newer varnish releases have been adapted to work better with upstart and follow now systemd policies for fedora and debian. This bug should now be closed.