[Bug 619246] Re: invoke-rc.d don't return same anwswer when the variable RUNLEVEL is setup at boot time
Dave Walker
davewalker at ubuntu.com
Thu May 26 10:21:08 UTC 2011
** Also affects: sysvinit (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: sysvinit (Ubuntu Lucid)
Status: New => Confirmed
** Changed in: sysvinit (Ubuntu Lucid)
Assignee: (unassigned) => Dave Walker (davewalker)
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.
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:
Confirmed
Bug description:
Binary package hint: sysvinit
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 :
We can try :
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
More information about the Ubuntu-sponsors
mailing list