Brandon Peirce <brandon_peirce <at> hotmail.com> writes:
> One thing I know is that backgrounding jobs can do special things with your > stdin/stdout and controlling terminal -- like attaching them to /dev/null if > they > are not explicitly redirected, or something like that IIRC. > Yes, I have come across this also. I am not too keen on exploring the permutations of x!>&y! :( > My loadavg dropped to near zero , they were both still in the test suite > phase. > Press enter on each respective terminal and get > on the host: > [1]+ Stopped ./pkgbld clean catalog > in the chroot (using ash shell): > [1] 17236 Stopped (tty input) ./build bash > Makes it look like a "feature" and NOTABUG :) > So I guess the answer is not to run Bash test suite in the background! Considering that it works when not run in the background this is definitely a solution. > Even better is to use GNU Screen (ftp://ftp.gnu.org/gnu/screen > or your favorite mirror). With that, you can run your script in the > foreground > in a dedicated "screen window" and you can even detach from the screen > session and log out and it continues to run as if in the foreground. Just > don't forget that it's running and reboot the host! > Dan mentioned this also. I will look into it. Thanks, Peter -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
