Re: /run/user/<id>/bb

[richard.purdie@linuxfoundation.org]

On Mon, 2019-01-07 at 10:07 -0600, Mark Hatle wrote:
> On 1/7/19 8:56 AM, Richard Purdie wrote:
> > On Thu, 2019-01-03 at 23:57 +0000, Slater, Joseph wrote:
> > > TMPDIR is useful, but named sockets need a "short" pathname, so
> > > it it
> > > might be nice to have a RUNDIR, or something similar, under
> > > /run/user/<id>/bb.  Could this be added?  I would do it if the
> > > concept is accepted.
> > 
> > What problem are we solving with this?
> > 
> > I'm guessing problems with memory resident bitbake in envvars but I
> > am
> > having to guess! :)
> 
> I'm assuming it's a combination of memory resident bitbake, and overall path
> length in TMPDIR to the sockets.  Sockets have a maximum filesystem path length
> (107 characters in Linux) that is much shorted then other components in the
> system (4k or less).
> 
> The typical way people work around this is whenever you use a socket
> you cd to the path of the socket and then open it relative to the
> current location.

The code in bitbake already does that as it happens...

> in either the TMPDIR or RUNDIR type configuration, that 'cd ; open'
> type behavior will still likely be needed.  So I'm not sure if RUNDIR
> actually fixes anything when it comes to path length issues.  It just
> moves the socket to a known location, from 'current' path.

I'm hoping Joe can explain the problem rather than us guessing,
particularly as the code for where I thought the problem may be already
does a chdir().

Cheers,

Richard