DL_DIR problems
Hello All,
We’re trying to share a DL_DIR over NFS so all developers don’t have to re-download source files every time they want to do a clean build. Unfortunately we’re running into problems with lock files that are left behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem?
Thanks,
Seth
Quoted 5 lines · Seth
We’re trying to share a
DL_DIRover NFS so all developers don’t have to re-download source files every time they want to do a clean build.
Unfortunately we’re running into problems with lock files that are left
behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem?
One option would be to maintain an internal downloads mirror, either populated by an autobuilder or by an rsync after engineer builds to the server hosting it. There'd be duplication in local disk space, but you'd avoid the NFS locking issues.
Signature · 5 lines
Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
Quoted 10 lines · Christopher Larson
Quoted 6 lines · Seth
We’re trying to share a
DL_DIRover NFS so all developers don’t have to re-download source files every time they want to do a clean build. Unfortunately we’re running into problems with lock files that are left behind by (sometimes) terminated processes. This will block users who are trying subsequent builds. How are others approaching this problem?
Quoted 4 lines
One option would be to maintain an internal downloads mirror, either populated by an autobuilder or by an rsync after engineer builds to the server hosting it. There'd be duplication in local disk space, but you'd avoid the NFS locking issues.
This is similar how the project infrastructure works.
nfs:/dl_dir
nfs:/rsynced_dl_dir
autobuilder uses the nfs:/dl_dir and a period rsync syncs to rsync_dl_dir. We can then use the rsync dir as our mirror. It ends up solving a few issues. If you don't want to run a full autobuilder, just a bitbake universe -c fetch on a cron job with all your layers would do it.
-b
Quoted 13 lines
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Signature · 3 lines
Elizabeth Flanagan Yocto Project Build and Release