Hi
I am wanting to time how long it takes a couple commands to run. I can do "time command" and it tells me. How do I do multple commands at a time. I tried: time command; command no good time "command; command" no good
I can make a script I guess but thought there was a more elegant way.
Thanks,
jerry
On Tue, Apr 10, 2007 at 01:34:23PM -0400, Jerry Geis wrote:
Hi
I am wanting to time how long it takes a couple commands to run. I can do "time command" and it tells me. How do I do multple commands at a time. I tried: time command; command no good time "command; command" no good
If using shell builtin time: time { cmd1; cmd2; }
or
time ( cmd1; cmd2 )
If using external command: /usr/bin/time sh -c "cmd1; cmd2"
On Tue, Apr 10, 2007 at 01:34:23PM -0400, Jerry Geis wrote:
I can do "time command" and it tells me.
time command; command
No, because you're saying time command command
time "command; command"
No because you're trying to run "command; command"
What you want is time ( command ; command )
Stephen Harris wrote:
On Tue, Apr 10, 2007 at 01:34:23PM -0400, Jerry Geis wrote:
I can do "time command" and it tells me.
time command; command
No, because you're saying time command command
time "command; command"
No because you're trying to run "command; command"
What you want is time ( command ; command )
Or if you've got a long series of commands you could stash them all in one shell script and then:
time scriptname
Correct?
Cheers,
chrism@imntv.com wrote:
Or if you've got a long series of commands you could stash them all in one shell script and then:
time scriptname
Correct?
Yes, as long as all of the actions in the script run synchronously. If one of them forks itself off into the background, time(1) won't see it since it only reports the lifetime of the shell script interpreter.
Stephen Harris wrote:
On Tue, Apr 10, 2007 at 01:34:23PM -0400, Jerry Geis wrote:
I can do "time command" and it tells me.
time command; command
No, because you're saying time command command
time "command; command"
No because you're trying to run "command; command"
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
On Wed, Apr 11, 2007 at 12:09:03PM -0400, Bisbal, Prentice wrote:
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
It works for me:
$ time (echo a ; echo b) a b
real 0m0.001s user 0m0.000s sys 0m0.001s
Luciano Miguel Ferreira Rocha wrote:
On Wed, Apr 11, 2007 at 12:09:03PM -0400, Bisbal, Prentice wrote:
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
It works for me:
$ time (echo a ; echo b) a b
real 0m0.001s user 0m0.000s sys 0m0.001s
What shell are you using? That doesn't work for me using Centos 4.4. My original command was time (ls; ls). I just tried you example and that doesn't work, either. I'm using bash.
On Wed, Apr 11, 2007 at 01:13:36PM -0400, Bisbal, Prentice wrote:
$ time (echo a ; echo b) a b
real 0m0.001s user 0m0.000s sys 0m0.001s
What shell are you using? That doesn't work for me using Centos 4.4. My original command was time (ls; ls). I just tried you example and that doesn't work, either. I'm using bash.
3.1.17 works (FC6); 3.00.16 doesn't (CentOS 4.4).
But the following works in every shell I tested (those before and also 2.05b, CentOS 3.8): time { echo a; echo b; } a b
real 0m0.000s user 0m0.000s sys 0m0.000s
Note that the following *has* to work everywhere, but also includes the penalty of starting a new shell: time sh -c 'echo a; echo b'
Luciano Miguel Ferreira Rocha wrote:
On Wed, Apr 11, 2007 at 12:09:03PM -0400, Bisbal, Prentice wrote:
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
It works for me:
$ time (echo a ; echo b) a b
real 0m0.001s user 0m0.000s sys 0m0.001s
There's no evidence there of what you're timing.
On Thu, Apr 12, 2007 at 06:41:24AM +0800, John Summerfield wrote:
Luciano Miguel Ferreira Rocha wrote:
It works for me:
$ time (echo a ; echo b) a b
real 0m0.001s user 0m0.000s sys 0m0.001s
There's no evidence there of what you're timing.
time (sleep 1; sleep 2)
real 0m3.008s user 0m0.001s sys 0m0.002s
time (ls -d /; dd if=/dev/zero of=/dev/null bs=16M count=3200) 3200+0 records in 3200+0 records out 53687091200 bytes (54 GB) copied, 1.49506 seconds, 35.9 GB/s
real 0m1.502s user 0m0.005s sys 0m1.428s
On Wed, Apr 11, 2007 at 12:09:03PM -0400, Bisbal, Prentice wrote:
Stephen Harris wrote:
time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
Hmm, interesting.
$ time ( echo hello )
It works in bash-2.03 on Solaris 8, but not in bash-2.05 in FC1, FC2, RHEL2.1 or Solaris 9 and not in bash-3.00 in RHEL4u4 or Solaris 10.
Works correctly in ksh88 and ksh93 on all platforms.
Sounds like a bash bug to me!
Stephen Harris wrote:
On Wed, Apr 11, 2007 at 12:09:03PM -0400, Bisbal, Prentice wrote:
Stephen Harris wrote:
time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
Hmm, interesting.
$ time ( echo hello )
It works in bash-2.03 on Solaris 8, but not in bash-2.05 in FC1, FC2, RHEL2.1 or Solaris 9 and not in bash-3.00 in RHEL4u4 or Solaris 10.
Works correctly in ksh88 and ksh93 on all platforms.
Sounds like a bash bug to me!
Thanks. For a second, I thought I was going crazy.
You could also put all your commands in a shell script then call your shell script like:
time /path/script.sh
Matt
On 4/11/07, Bisbal, Prentice PBisbal@lexpharma.com wrote:
Stephen Harris wrote:
On Tue, Apr 10, 2007 at 01:34:23PM -0400, Jerry Geis wrote:
I can do "time command" and it tells me.
time command; command
No, because you're saying time command command
time "command; command"
No because you're trying to run "command; command"
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
-- Prentice
The contents of this communication, including any attachments, may be confidential, privileged or otherwise protected from disclosure. They are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please do not read, copy, use or disclose the contents of this communication. Please notify the sender immediately and delete the communication in its entirety. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Matt Shields wrote:
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
That's interesting - it works in FC6 but not Centos 4.x (no output from time).
Bisbal, Prentice wrote:
Stephen Harris wr
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
summer@Lyrebird:~> time { sleep 10s;sleep 10s;}
real 0m20.023s user 0m0.000s sys 0m0.008s summer@Lyrebird:~> [summer@bilby ~]$ time (sleep 5s;sleep 5s) [summer@bilby ~]$
John Summerfield wrote:
Bisbal, Prentice wrote:
Stephen Harris wr
What you want is time ( command ; command )
I was going to suggest that myself, but when I tested in in bash, it didn't work for me. Does it work for you?
summer@Lyrebird:~> time { sleep 10s;sleep 10s;}
real 0m20.023s user 0m0.000s sys 0m0.008s summer@Lyrebird:~> [summer@bilby ~]$ time (sleep 5s;sleep 5s) [summer@bilby ~]$
summer@Lyrebird:~> time (sleep 10s;sleep 10s)
real 0m20.019s user 0m0.000s sys 0m0.000s summer@Lyrebird:~>
Lyrebird's OpenSUSE 10.2, bash 3.1.17, Bilby's nahantish.
-
Bisbal, Prentice -
chrism＠imntv.com -
Jerry Geis -
John Summerfield -
Les Mikesell -
Luciano Miguel Ferreira Rocha -
Matt Shields -
Stephen Harris -
Warren Young