From owner-freebsd-bugs  Thu Jul 23 11:53:42 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA09922
          for freebsd-bugs-outgoing; Thu, 23 Jul 1998 11:53:42 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09914;
          Thu, 23 Jul 1998 11:53:39 -0700 (PDT)
          (envelope-from kargl@troutmask.apl.washington.edu)
Received: (from kargl@localhost)
	by troutmask.apl.washington.edu (8.8.8/8.8.5) id LAA02527;
	Thu, 23 Jul 1998 11:52:30 -0700 (PDT)
From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu>
Message-Id: <199807231852.LAA02527@troutmask.apl.washington.edu>
Subject: Re: bin/7368: Added options to /usr/bin/time
In-Reply-To: <430.901218469@critter.freebsd.dk> from Poul-Henning Kamp at "Jul 23, 98 08:27:49 pm"
To: phk@critter.freebsd.dk (Poul-Henning Kamp)
Date: Thu, 23 Jul 1998 11:52:30 -0700 (PDT)
Cc: freebsd-bugs@FreeBSD.ORG, freebsd-gnats-submit@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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