Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Markus Lehtonen <markus.lehtonen@linux.intel.com>,
	Andreas Oberritter <obi@opendreambox.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] update-rc.d.bbclass: check that init script exists before running it
Date: Thu, 06 Oct 2016 11:12:22 +0100	[thread overview]
Message-ID: <1475748742.16008.29.camel@pbcl.net> (raw)
In-Reply-To: <1475743775.13655.55.camel@linux.intel.com>

On Thu, 2016-10-06 at 11:49 +0300, Markus Lehtonen wrote:
> On Wed, 2016-10-05 at 16:51 +0200, Andreas Oberritter wrote:
> > Hello Markus,
> > 
> > On 05.10.2016 16:11, Markus Lehtonen wrote:
> > > Check that the init script that is going to be called in the
> > > prerm()
> > > script really exists. There might be a packaging bug or the
> > > script
> > > might've been removed already earlier in prerm().
> > 
> > isn't it called prerm in the first place because it's not supposed
> > to
> > remove any packaged files?
> 
> In the case of this bug it does not remove any packaged files. Update
> -alternatives removes a symlink (created by itself)

That arguably is a bug in u-a, which probably ought to be removing the
symlink in postrm not prerm.  If it removes the symlink too early and
prevents u-rc.d from running "stop" on it then you may end up with
dangling daemon processes still running after the package has been
uninstalled.  But...

> I think that the pre post etc scripts should basically never fail.

... this is essentially true, and having u-rc.d's own prerm fail
because of a bug in u-a definitely isn't going to improve the
situation.  So I think your patch is a good one.

p.

> 


  reply	other threads:[~2016-10-06 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-05 14:11 [PATCH] update-rc.d.bbclass: check that init script exists before running it Markus Lehtonen
2016-10-05 14:51 ` Andreas Oberritter
2016-10-06  8:49   ` Markus Lehtonen
2016-10-06 10:12     ` Phil Blundell [this message]
2016-10-06 13:46       ` Markus Lehtonen
2016-10-06 15:12         ` Phil Blundell
2016-10-08 14:41           ` Andreas Oberritter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1475748742.16008.29.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=markus.lehtonen@linux.intel.com \
    --cc=obi@opendreambox.org \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox