[Bug 619246] Re: invoke-rc.d don't return same anwswer when the variable RUNLEVEL is setup at boot time

[Launchpad Bug Tracker]

This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu17.3

---------------
sysvinit (2.87dsf-4ubuntu17.3) lucid-proposed; urgency=low

  * debian/sysv-rc/sbin/invoke-rc.d: replace RUNLEVEL with RUNLEVELHELPER.
    Using RUNLEVEL causes spurious failures when invoke-rc.d is invoked
    with RUNLEVEL already defined in the environment (as it is e.g. during
    bootup) since invoke-rc.d's RUNLEVEL will become an exported variable
    at that point and cause /sbin/runlevel to return bad data. (LP: #619246)
 -- James Troup <james.troup at canonical.com>   Tue, 24 May 2011 11:41:45 +0000

** Changed in: sysvinit (Ubuntu Lucid)
       Status: Fix Committed => Fix Released

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

Title:
  invoke-rc.d don't return same anwswer when the variable RUNLEVEL is
  setup at boot time

Status in “sysvinit” package in Ubuntu:
  Fix Released
Status in “sysvinit” source package in Lucid:
  Fix Released

Bug description:
  Binary package hint: sysvinit

  IMPACT: puppet tool uses invoke-rc.d to determine if a service is
  launched at boot time. But at boot time, a variable RUNLEVEL is setup
  and invoke-rc.d doesn't work after that.

  FIX: have invoke-rc.d to use 'RUNLEVELHELPER' as the variable name for
  the full path to the runlevel(8) binary instead of 'RUNLEVEL'.

  PATCH: See comment #3, or diff for (2.87dsf-4ubuntu24) oneiric.

  REPRODUCE: 
  RUNLEVEL=2 bash -x /usr/sbin/invoke-rc.d --quiet --query ssh start
  -> we can see an exit 105
  but :
  bash -x /usr/sbin/invoke-rc.d --quiet --query ssh start
  -> we can see an exit 104 (the good answer)

  With debian lenny :
  RUNLEVEL=2 bash -x /usr/sbin/invoke-rc.d --quiet --query ssh start
  -> we can see an exit 104

  DISCUSSION: Regression potential is low, it is a back-ported fix from
  oneiric.  This fix is currently in production use on some Canonical
  Lucid servers.