[Bug 920811] Re: start: Unknown parameter: JOB

Stéphane Graber stgraber at stgraber.org
Tue Jan 24 04:26:35 UTC 2012


Not worth fixing for existing releases as the return value is discarded
and so it won't break an update, still, ifupdown's maintainer scripts
should never try to restart any of the networking jobs (as most of them
don't know how to handle a "stop").

Will look into this for Precise (including other packages that may have
the same issue with upstart job instances).

** Changed in: ifupdown (Ubuntu)
       Status: New => Triaged

** Changed in: ifupdown (Ubuntu)
     Assignee: (unassigned) => Stéphane Graber (stgraber)

** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => Low

-- 
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/920811

Title:
  start: Unknown parameter: JOB

Status in “ifupdown” package in Ubuntu:
  Triaged

Bug description:
  Got this when upgrading an lucid i386 chroot, please close if not
  relevant

  Preparing to replace ifupdown 0.6.8ubuntu29 (using .../ifupdown_0.6.8ubuntu29.2_i386.deb) ...
  ...
  Setting up ifupdown (0.6.8ubuntu29.2) ...
  start: Unknown parameter: JOB

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




More information about the foundations-bugs mailing list