sablink/build
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[bin] implement read, shared lock in emerge()

Browse Source
This commit is contained in:
Fabio Erculiani 2012-09-06 14:29:11 +02:00
parent b14075158c
commit de5b95bdd2
1 changed files with 21 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
bin/buildrc
View File

@ -1,21 +1,32 @@
# Emerge wrapper, uses matter lock file support to avoid
# concurrent execution
emerge() {
snapshot_lock_file=/var/tmp/.emerge.snapshot.lock"
matter_lock_file="/var/tmp/.matter_resource.lock"
flock -x -n "${matter_lock_file}" true
rc=${?}
if [ "${rc}" != "0" ]; then
echo
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"
echo "matter is running on this chroot, in order to prevent explosions"
echo "this emerge instance will terminate NOW"
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~"
echo
echo >&2
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" >&2
echo "matter is running on this chroot, in order to prevent explosions" >&2
echo "this emerge instance will terminate NOW" >&2
echo "~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~" >&2
echo >&2
return 1
else
# eval $(portageq envvar -v FETCHCOMMAND RESUMECOMMAND PORTAGE_RSYNC_OPTS)
# add bandwidth limit here
/usr/bin/emerge --quiet-build=n "$@"
return ${?}
# acquire snapshot read lock in non-blocking, shared mode
(
flock -s -n 9 || {
echo "Hello there," >&2;
echo "a chroot snapshot is in progress..." >%2;
echo "Try again later." >&2;
exit 1;
}
# eval $(portageq envvar -v FETCHCOMMAND RESUMECOMMAND PORTAGE_RSYNC_OPTS)
# add bandwidth limit here
/usr/bin/emerge --quiet-build=n "$@"
exit ${?}
) 9> "${snapshot_lock_file}"
return "${?}"
fi
}