Re: 100% cpu with: while true ;do read /dev/null ;done

On Thu, Oct 22, 2009 at 12:15 AM, Jo King joki...@yahoo.co.uk wrote: Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu'

Re: set -e in bash 4

On Wed, Oct 21, 2009 at 09:56:49PM -0400, Chet Ramey wrote: Yes, this is the intended behavior. Thanks for clarifying. This is one of the things that came out of the discussions among the Posix working group. It also matches historical practice. I searched the archives and found this

Re: 100% cpu with: while true ;do read /dev/null ;done

thanks for reply. agree it's not a bug with bash. i am inclinded to agree with the comments but bash is popular and attracts a lot of newbies into scripting - a bit of smart 'correction' of their wrong ways would at least keep the cpu available for other processes (even a sleep for 100ms