Your message dated Sat, 25 Jan 2014 03:15:57 +0000
with message-id <[email protected]>
and subject line Bug report contradicts status_of_proc documentation
has caused the Debian Bug report #688844,
regarding winbind init script not LSB compliant
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
688844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688844
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: winbind
Version: 3.6.6-3_amd64
winbind init script is not LSB compliant: the status function returns 4
instead of 3 when the daemon is stopped
repro:
apt-get install winbind
/etc/init.d/winbind stop
/etc/init.d/winbind status; echo $?
this happens because the status_of_proc call has wrong parameter ordering.
Attached patch fixes the issue.
Tags: patch
winbind_init_lsb.patch
Description: Binary data
--- End Message ---
--- Begin Message ---
The current behaviour is consistent with the status_of_proc
documentation on the Debian Wiki. See
https://wiki.debian.org/LSBInitScripts/StatusSupport which suggests
passing -p first.
I also can't reproduce this bug report:
gwenhwyvar:/home/jelmer# /etc/init.d/winbind start
[ ok ] Starting the Winbind daemon: winbind.
gwenhwyvar:/home/jelmer# /etc/init.d/winbind stop
[ ok ] Stopping the Winbind daemon: winbind.
gwenhwyvar:/home/jelmer# /etc/init.d/winbind status; echo $?
[FAIL] winbind is not running ... failed!
3
signature.asc
Description: Digital signature
--- End Message ---
