* Joshua Judson Rosen <[email protected]> [18.03.2013 19:32]: > >>[ -e "$file" ]&& . "$file" > >> > >>not ok for you? my usecase was more a "speed" issue, because > > > >The only technical reason against that is the race condition if $file is > >deleted after the existence/read check. > > Yes. And there's no way to get around the shell aborting in that case.
maybe something like: cp "$file" "/tmp/include_$$" || . "/tmp/include_$$" but this is really ugly. bye, bastian _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
