All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: why does useradd.bbclass loop retrying its commands?
Date: Sat, 15 Nov 2014 15:19:32 -0600	[thread overview]
Message-ID: <5467C364.7080008@windriver.com> (raw)
In-Reply-To: <5466E6B7.2050609@pabigot.com>

On 11/14/14, 11:37 PM, Peter A. Bigot wrote:
> The useradd, groupadd, and groupmems commands in useradd.bbclass are
> executed in a loop with up to 10 failed attempts before they give up.
> This appears to have always been the case, as long as that file has been
> present.

If multiple recipes/packages have the user, group, or shadow databases open -- 
the system will block until they are done maniuplating the file.

> Is there any reason why an initial failed attempt to execute one of
> these commands would be expected to succeed on retry, other than because
> delaying failure gives a chance for concurrently executing task to
> complete and so satisfy a dependency?

Depending on system, cores, etc.. we've seen easily it take up to 5-7 tries 
before the files unlock and are available for processing.

--Mark

> (This isn't the root cause of the pseudo autobuilder failure under
> multilib, but it did look plausible for a while.)
>
> Peter
>



      parent reply	other threads:[~2014-11-15 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15  5:37 why does useradd.bbclass loop retrying its commands? Peter A. Bigot
2014-11-15 16:22 ` Richard Purdie
2014-11-15 16:53   ` Peter A. Bigot
2014-11-15 21:19 ` Mark Hatle [this message]

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=5467C364.7080008@windriver.com \
    --to=mark.hatle@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.