Jack Lloyd wrote:
> On Thu, Sep 13, 2007 at 10:21:26PM -0400, Chet Ramey wrote:
>> `time' is not a builtin; it is a shell reserved word that causes timing
>> information to be printed when `waitpid' returns. It's a synchronous
>> operation that doesn't interact as you'd like with job control.
>
>
On Thu, Sep 13, 2007 at 10:21:26PM -0400, Chet Ramey wrote:
>
> `time' is not a builtin; it is a shell reserved word that causes timing
> information to be printed when `waitpid' returns. It's a synchronous
> operation that doesn't interact as you'd like with job control.
Ah, I see. Is there any
Jack Lloyd wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: x86_64-redhat-linux-gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
> -D
Jack Lloyd wrote:
Description:
The time builtin seems to be confused if something is
backgrounded, and prints immediately the time rather than
waiting for the job to complete. I found this very unexpected.
Repeat-By:
$ time sleep 5
# hit C-Z to stop the job before 5 se
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-redhat-linux-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDI
