Re: [PATCH] useradd: don't override pseudo environment

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2017-09-15 at 12:58 -0500, Seebs wrote:
> On Fri, 15 Sep 2017 12:58:48 +0100
> Ross Burton <ross.burton@intel.com> wrote:
> 
> > 
> > Remove the PSEUDO_LOCALSTATEDIR assignment and inherit the correct
> > assignment in FAKEROOTENV.
> Nice catch! This probably explains a LOT of the strange behaviors
> we've been seeing.

I think it will fix some warnings but I believe the bulk of the issues
are from files being deleted in contents outside of pseudo and then the
inode numbers being reused.

Note that this issue existed long before we had recipe specific
sysroots.

Unfortunately its very hard to guarantee we'll always delete files
under pseudo context as for example "do_clean",
"do_recipe_prepare_sysroot" and others are not pseudo tasks but can
add/delete files. Files in ${WORKDIR}/temp such as log files and
sysroot manifests and locks may be modified by both the fakeroot worker
and the parent bitbake server too.

Possible options:

a) Add a way to filter the paths pseudo looks at and cares about.
b) At server startup, check files really do exist
c) Add some way to trigger a sync of the pseudo db with what is on 
   disk.

Cheers,

Richard