Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 23 Jul 1998 12:00:02 -0700 (PDT)
From:      "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
To:        freebsd-bugs@FreeBSD.ORG
Subject:   Re: bin/7368: Added options to /usr/bin/time
Message-ID:  <199807231900.MAA11499@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/7368; it has been noted by GNATS.

From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Cc: freebsd-bugs@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: bin/7368: Added options to /usr/bin/time
Date: Thu, 23 Jul 1998 11:52:30 -0700 (PDT)

 According to Poul-Henning Kamp:
 > In message <199807231650.JAA01687@freefall.freebsd.org>, "Steven G. Kargl" writ
 > es:
 > >The following reply was made to PR bin/7368; it has been noted by GNATS.
 > >
 > >From: "Steven G. Kargl" <kargl@apl.washington.edu>
 > >To: freebsd-gnats-submit@freebsd.org, kargl@troutmask.apl.washington.edu
 > >Cc:  Subject: Re: bin/7368: Added options to /usr/bin/time
 > >Date: Thu, 23 Jul 1998 09:45:43 -0700
 > >
 > > I've sent followups to both Dag-Erling and Niall in private
 > > email before I realized,  I could/should document my rebuttal
 > > here.
 > > 
 > > How does one redirect via a shell the output of /usr/bin/time
 > > without redirecting the output from the command that is being
 > > timed. The answer is you can't, and is the motivation for the new
 > > options.
 > 
 > 
 > will
 > 
 > 	time csh -c "foocommand >& foo.out" >& time.out
 > 
 > do ?
 > 
 > (I'm not against the addition as such, as long as current
 > behaviour isn't changed.)
 > 
 
 Current behavior is unchanged.  I've added options.  Your suggest
 seems to work (I learn something new everyday).
 
 However, consider
 
 foreach i (*.dat)
 time -a time.out foocommand $i
 end
 
 foreach i (*.c)
 time csh -c "foocommand $i" >>& time.out
 end
 
 One of these seems to be easier to remember for those who
 are not great at shell programmer.
 
 The former times the execution of foocommand while the later times
 the execution of csh + foocommand.  If the execution time of csh
 is small in comparison the execution time of foocommand, then ones
 statistics may not be too tainted.  But, what happens if csh time
 swamps foocommand.
 
 -- 
 Steve
 
 finger kargl@troutmask.apl.washington.edu
 http://troutmask.apl.washington.edu/~clesceri/kargl.html

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807231900.MAA11499>