[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#208010: [PROPOSAL] init script LSB 1.3 compliance

On Wed, Sep 03, 2003 at 09:20:15PM +0200, Martin Godisch wrote:
> On Wed, Sep 03, 2003 at 17:44:49 +0200, Wouter Verhelst wrote:
> > > +	      <tag>7</tag>
> > > +	      <item>program is not running,</item>
> > 
> > This one will break removing and upgrading packages; dpkg checks the
> > exit code of maintainer scripts, assuming they failed if the exit code
> > was nonzero. Given the fact it is recommended by policy to use set -e in
> > maintainer scripts, dpkg will pick up this exit code and mark the
> > package as failed in the deconfiguration phase.  Either this requirement
> > should be removed, or policy should warn maintainers of that fact.
> In the deconfiguration phase "invoke-rc.d package stop" is run. What
> error do you imagine here, which should not be reported to/by dpkg?

invoke-rc.d will pass the exit state on. According to invoke-rc.d's
manpage, a non-zero exit state "usually indicates a failure".

That isn't the case here; when the 'stop' target is invoked, and the
program wasn't running, a non-zero exit code is issued, even though the
status is actually what is requested.

Dpkg will consider any non-zero exit state as 'failed', and will stop
uninstalling the package.

Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
"Stop breathing down my neck." "My breathing is merely a simulation."
"So is my neck, stop it anyway!"
  -- Voyager's EMH versus the Prometheus' EMH, stardate 51462.

Attachment: pgpBklSykn2FK.pgp
Description: PGP signature

Reply to: