[Varnish] #1680: varnish init.d script status has no output

[Varnish]

#1680: varnish init.d script status has no output
-----------------------+-------------------------
 Reporter:  razvanphp  |       Owner:  lkarsten
     Type:  defect     |      Status:  closed
 Priority:  normal     |   Milestone:
Component:  packaging  |     Version:  4.0.3
 Severity:  normal     |  Resolution:  worksforme
 Keywords:             |
-----------------------+-------------------------
Changes (by lkarsten):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 Hi.

 This change was introduced as part of importing downstream packaging
 changes from Debian.
 See commit 74c3c3bb037e1c54ed9ebd64da94090587c6f05d for details.

 I tested the behavior on wheezy, and as far as I can see start-stop-daemon
 behaves as you would expect it to.

 {{{
 root at wheezy-amd64:~# varnishd -V
 varnishd (varnish-4.0.3 revision b8c4a34)
 Copyright (c) 2006 Verdens Gang AS
 Copyright (c) 2006-2014 Varnish Software AS

 root at wheezy-amd64:~# service varnish start
 [ ok ] Starting HTTP accelerator: varnishd.
 root at wheezy-amd64:~# /etc/init.d/varnish status; echo $?
 0

 root at wheezy-amd64:~# service varnish stop
 [ ok ] Stopping HTTP accelerator: varnishd.
 root at wheezy-amd64:~# /etc/init.d/varnish status; echo $?
 3

 root at wheezy-amd64:~# service varnish start
 [ ok ] Starting HTTP accelerator: varnishd.
 root at wheezy-amd64:~# pkill varnishd
 root at wheezy-amd64:~# /etc/init.d/varnish status; echo $?
 1
 }}}

 This is according to exit status documented in start-stop-daemon(8).

 If you want to output something after checking, you can use the contents
 of $?.
 {{{
 root at wheezy-amd64:~# /etc/init.d/varnish status && echo running
 running
 }}}

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1680#comment:2>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator