All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Host contamination that isn't
Date: Tue, 8 Mar 2016 14:33:28 +0100	[thread overview]
Message-ID: <56DED4A8.6070009@mlbassoc.com> (raw)

I'm getting a lot of messages like this:
   amanda: /amanda/usr/sbin/amtoc is owned by uid 1000, which is the same as the user running bitbake. This may be due 
to host contamination
   amanda: /amanda/usr/sbin/amcrypt-ossl is owned by uid 1000, which is the same as the user running bitbake. This may 
be due to host contamination
   amanda: /amanda/usr/sbin/amvault is owned by uid 1000, which is the same as the user running bitbake. This may be due 
to host contamination

In reality, this is not really a problem.  I'm building a recipe
which adds a user to my system image that just happens to have the
same UID as mine (first user added, go figure).  So the messages in
this case are quite bogus.

How can I avoid them?  When I add my extra user to my image, is
there a way to force the UID/GID to something I know is "safe"?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2016-03-08 13:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 13:33 Gary Thomas [this message]
2016-03-09  7:50 ` Host contamination that isn't Gary Thomas
2016-03-09  8:28   ` Gary Thomas
2016-03-15 11:44     ` Burton, Ross
2016-03-15 13:44       ` Gary Thomas

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=56DED4A8.6070009@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=yocto@yoctoproject.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.