diff options
| author | kensmith <kensmith@FreeBSD.org> | 2004-08-06 20:08:38 +0000 |
|---|---|---|
| committer | kensmith <kensmith@FreeBSD.org> | 2004-08-06 20:08:38 +0000 |
| commit | 03511301305e678b24db3dfe6bb540644aaad01d (patch) | |
| tree | f388fa4d65a798db7eafdd003d5a5fc2e7e42630 /release/scripts | |
| parent | f67e9133471b72753415b74d6ee42bab159d2232 (diff) | |
| download | FreeBSD-src-03511301305e678b24db3dfe6bb540644aaad01d.zip FreeBSD-src-03511301305e678b24db3dfe6bb540644aaad01d.tar.gz | |
I've had 'make release' problems on a large/fast dual processor machine
with doFS.sh consistently dying here because the device didn't exist
in the namespace fast enough after doing the mdconfig. But the device
did eventually show up. There have been similar complaints on mailing
lists that might boil down to this being the problem too.
This is obviously a hack, if anyone knows what might cause a delay
between mdconfig running and when the name appears in the /dev namespace
(inside a chroot-ed environment if that matters) I'd be happy to back
this out.
Diffstat (limited to 'release/scripts')
| -rw-r--r-- | release/scripts/doFS.sh | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/release/scripts/doFS.sh b/release/scripts/doFS.sh index b61c7ed..e70dcb9 100644 --- a/release/scripts/doFS.sh +++ b/release/scripts/doFS.sh @@ -64,6 +64,8 @@ dofs_md () { fi MDDEVICE=`mdconfig -a -t vnode -f ${FSIMG}` + # This sleep is needed to solve some sort of race condition + sleep 5 if [ ! -c /dev/${MDDEVICE} ] ; then echo "No /dev/$MDDEVICE" 1>&2 exit 1 |
