[DRE-maint] Bug#677827: chef init script does not report status or start/stop success/fail properly

[Eric Blevins]

Package: chef
Version: 0.10.10-2
Severity: important

Dear Maintainer,

service chef status does not report properly
service chef start/stop always reports failure

The problem occurs because the process name is "ruby" instead of "chef-client" like the init script expects.

Changing the shebang from:

#!/usr/bin/env ruby
to
#!/usr/bin/ruby1.8

fixes the issue.

Another way to fix it is to change the init script:
--- chef-client.original	2012-06-16 23:00:11.120402985 -0400
+++ chef-client	2012-06-16 23:00:58.156403000 -0400
@@ -45,7 +45,7 @@
 running() {
   [ ! -f "$PIDFILE" ] && return 1
   pid=`cat $PIDFILE`
-  running_pid $pid $NAME || return 1
+  running_pid $pid ruby || return 1
   return 0
 }




-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chef depends on:
ii  debconf [debconf-2.0]       1.5.43
ii  ohai                        6.14.0-1
ii  ruby-bunny                  0.7.8-1
ii  ruby-erubis [erubis]        2.7.0-1
ii  ruby-highline               1.6.12-1
ii  ruby-json                   1.7.3-1
ii  ruby-mixlib-authentication  1.1.4-1
ii  ruby-mixlib-cli             1.2.2-1
ii  ruby-mixlib-config          1.1.2-2
ii  ruby-mixlib-log             1.3.0-1
ii  ruby-mixlib-shellout        1.0.0-1
ii  ruby-moneta                 0.6.0-3
ii  ruby-net-ssh                1:2.5.1-1
ii  ruby-net-ssh-multi          1.1-1
ii  ruby-rest-client            1.6.7-1
ii  ruby-treetop                1.4.10-4
ii  ruby-uuidtools              2.1.2-1
ii  ruby-yajl                   1.0.0-1
ii  ruby1.8 [ruby-interpreter]  1.8.7.358-4

chef recommends no packages.

chef suggests no packages.

-- debconf information excluded