bitbake.lock?

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
------------------------------------------------------------

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

see
http://git.openembedded.org/bitbake/commit/?id=6004cbf36c980c2574c1c9153df81a7c55317e17

and
http://bugzilla.pokylinux.org/show_bug.cgi?id=1464

Martin 'JaMa' Jansa     jabber: [email protected]