Last modified: 2014-08-04 02:49:15 UTC
$ /etc/init.d/diamond status Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service diamond status Since the script you are attempting to invoke has been converted to an Upstart job, you may also use the status(8) utility, e.g. status diamond diamond stop/waiting -- That makes sense. Now: $ service diamond Usage: /etc/init.d/diamond COMMAND --- $ service diamond help Rather than invoking init scripts through /etc/init.d, use the service(8) utility, e.g. service diamond help --- Those look wrong.
AFAICS, this only happens for "service diamond help": | scfc@tools-login:~$ service diamond help | Rather than invoking init scripts through /etc/init.d, use the service(8) | utility, e.g. service diamond help | The script you are attempting to invoke has been converted to an Upstart | job, but help is not supported for Upstart jobs. | scfc@tools-login:~$ service diamond start | start: Rejected send message, 1 matched rules; type="method_call", sender=":1.150" (uid=2267 pid=19081 comm="start diamond ") interface="com.ubuntu.Upstart0_6.Job" member="Start" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init") | scfc@tools-login:~$ service toolwatcher status | toolwatcher start/running, process 868 | scfc@tools-login:~$ service toolwatcher help | toolwatcher: unrecognized service | scfc@tools-login:~$ The problem seems to be rooted upstream.
