summaryrefslogtreecommitdiff
path: root/meta/recipes-support/db
diff options
context:
space:
mode:
authorScott Garman <scott.a.garman@intel.com>2010-10-08 14:40:47 -0700
committerScott Garman <scott.a.garman@intel.com>2010-10-08 14:48:20 -0700
commitc805a6ed281279ef0ccc4e6e084d52a725260e09 (patch)
tree89868cd32164b13e7e76fb42dac7b735358d2248 /meta/recipes-support/db
parent7cd824a5388f7284a1252e9f61af2c88d26ca163 (diff)
downloadopenembedded-core-c805a6ed281279ef0ccc4e6e084d52a725260e09.tar.gz
openembedded-core-c805a6ed281279ef0ccc4e6e084d52a725260e09.tar.bz2
openembedded-core-c805a6ed281279ef0ccc4e6e084d52a725260e09.tar.xz
openembedded-core-c805a6ed281279ef0ccc4e6e084d52a725260e09.zip
poky-qemu-internal: implement file locking in bash
There does not appear to be a universal lockfile utility that meets our needs. For example: * 'lockfile' is part of the procmail pacakge in Ubuntu, a requirement we don't want to impose on our users * lockfile-[create|remove] from the Ubuntu lockfile-progs package does not appear to be available in Fedora/openSUSE So, the most portable way to do this is just to implement it in bash. The likelihood of race conditions is minimal for what we need this for. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Diffstat (limited to 'meta/recipes-support/db')
0 files changed, 0 insertions, 0 deletions