[Bug 722783] Re: Upstart scripts broken for status command

[Stéphane Graber]

Right, that's because it's an upstart instance, here's an example:

root at castiana:~# status network-interface
status: Unknown parameter: INTERFACE

root at castiana:~# status network-interface INTERFACE=eth0
network-interface (eth0) start/running


"initctl list" can be used as a way to get the value you want for the
needed variable

** Changed in: ifupdown (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/722783

Title:
  Upstart scripts broken for status command

Status in “ifupdown” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ifupdown

  On ubuntu lucid (version 0.6.8ubuntu29.2): (but looking at the upstart
  files in natty, i don't see any changes)

  The status (and initctl status) command is broken for network-
  interface and network-interface-security. The initctl man page says
  the command should be returning a status for each instance (much like
  the output of initctl list does), but it instead just returns an error
  unless you specify an instance. This breaks service state detection in
  bcfg2.

  # initctl status network-interface
  initctl: Unknown parameter: INTERFACE

  # initctl status network-interface-security
  initctl: Unknown parameter: JOB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/722783/+subscriptions