* bitbake.lock?
@ 2012-01-23 22:12 Gary Thomas
2012-01-23 22:31 ` bitbake.lock? Chris Larson
2012-01-23 22:49 ` bitbake.lock? Martin Jansa
0 siblings, 2 replies; 3+ messages in thread
From: Gary Thomas @ 2012-01-23 22:12 UTC (permalink / raw)
To: openembedded-core
I've noticed that recent versions of bitbake leave this file
in the build directory.
What is it for & why is it left around?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bitbake.lock?
2012-01-23 22:12 bitbake.lock? Gary Thomas
@ 2012-01-23 22:31 ` Chris Larson
2012-01-23 22:49 ` bitbake.lock? Martin Jansa
1 sibling, 0 replies; 3+ messages in thread
From: Chris Larson @ 2012-01-23 22:31 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
On Mon, Jan 23, 2012 at 3:12 PM, Gary Thomas <gary@mlbassoc.com> wrote:
> I've noticed that recent versions of bitbake leave this file
> in the build directory.
>
> What is it for & why is it left around?
It's used to ensure only one bitbake runs against a given build
directory at a time. I'm not sure why it's left around, it seems like
some of the ways in which bitbake exits don't result in a cleanup. I'm
sure Richard would know for sure.
Just as an FYI, it does check the pid stored there against the running
processes, so if it errors out indicating there's a second bitbake
running, there really is, even if you don't know it. Could have a
remnant process from a previous build, depending on how it exited,
I've noticed. Particularly hitting the parse error hang issue can
result in remnant processes hanging around monopolizing the build dir.
kill is our friend in those cases. I just wanted to note this to
ensure that no one physically removes the .lock when encountering the
error.
--
Christopher Larson
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bitbake.lock?
2012-01-23 22:12 bitbake.lock? Gary Thomas
2012-01-23 22:31 ` bitbake.lock? Chris Larson
@ 2012-01-23 22:49 ` Martin Jansa
1 sibling, 0 replies; 3+ messages in thread
From: Martin Jansa @ 2012-01-23 22:49 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
On Mon, Jan 23, 2012 at 03:12:35PM -0700, Gary Thomas wrote:
> I've noticed that recent versions of bitbake leave this file
> in the build directory.
>
> What is it for & why is it left around?
see
http://git.openembedded.org/bitbake/commit/?id=6004cbf36c980c2574c1c9153df81a7c55317e17
and
http://bugzilla.pokylinux.org/show_bug.cgi?id=1464
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-01-23 22:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-23 22:12 bitbake.lock? Gary Thomas
2012-01-23 22:31 ` bitbake.lock? Chris Larson
2012-01-23 22:49 ` bitbake.lock? Martin Jansa
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox