[NTLUG:Discuss] let me try that again - time
MadHat
madhat at unspecific.com
Fri May 30 10:20:54 CDT 2003
On Fri, 2003-05-30 at 10:05, Darin W. Smith wrote:
> I think what you may be encountering is that bash itself has a builtin
> 'time' reserved word. It does what time(1) does, it times a command. It
> understands one option, -p, which directs it to produce POSIX-compliant
> output.
>
> My time(1) manpage shows that it has exactly the same format and options as
> the bash builtin.
>
> Try "time command" vs. "/usr/bin/time command"
>
> They seem to work identically for me, as does "time -p command" and
> "/usr/bin/time -p command"
>
> What options, besides -p, are you trying to use? I don't see any other
> options specified when I do:
> man 1 time
> OR
> man bash (and search for time)
>
D'OH!!! I forgot about that. That is what the issue is.
I knew it was shell specific, but forgot about the builtin time.
$ /usr/bin/time --version
GNU time 1.7
-f for format
-o for output file
-a for append to said output file
-v for verbose output (see below)
Command being timed: "ls -la"
User time (seconds): 0.00
System time (seconds): 0.00
Percent of CPU this job got: 1%
Elapsed (wall clock) time (h:mm:ss or m:ss): 0:01.77
Average shared text size (kbytes): 0
Average unshared data size (kbytes): 0
Average stack size (kbytes): 0
Average total size (kbytes): 0
Maximum resident set size (kbytes): 0
Average resident set size (kbytes): 0
Major (requiring I/O) page faults: 197
Minor (reclaiming a frame) page faults: 44
Voluntary context switches: 0
Involuntary context switches: 0
Swaps: 0
File system inputs: 0
File system outputs: 0
Socket messages sent: 0
Socket messages received: 0
Signals delivered: 0
Page size (bytes): 4096
Exit status: 0
--
MadHat at Unspecific.com
`But I don't want to go among mad people,' Alice remarked.
`Oh, you can't help that,' said the Cat: `we're all mad here...'
-- Lewis Carroll - _Alice's_Adventures_in_Wonderland_
More information about the Discuss
mailing list