Date: Mon, 8 Apr 2002 06:20:02 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/36874: time(1): invalid arguments Message-ID: <200204081320.g38DK2v09056@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/36874; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: Edwin Groothuis <edwin@mavetju.org> Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: bin/36874: time(1): invalid arguments Date: Mon, 8 Apr 2002 23:17:03 +1000 (EST) On Mon, 8 Apr 2002, Edwin Groothuis wrote: > On Mon, Apr 08, 2002 at 02:46:29PM +0200, aaron wrote: > > >Description: > > ... > > aaron@meta:~> time -l ls > > bash: -l: command not found > > ^^^^^^^^^^^^^^ ---- oops! > > real 0m0.004s > > user 0m0.001s > > sys 0m0.002s > > > > > > HOWEVER: when you type in in: > > /usr/bin/time -l ls > > > > everything works as expected. > > time (without the path) is the one which is implemented in your shell. > /usr/bin/time (with the path) is the one which is coming with the system. > > If you're using bash, see "man bash" and search for time. I couldn't even find a way to tell bash-2 to stop using its broken time(!1). `time' in bash-2 is a keyword, not a builtin, so I couldn't find a way to override it using aliases or shell functions . My solution for this was to upgrade to bash-1 :-), but i still notice the brokenness when I run something like "time tar cf foo bar" ... ^Z. The broken time prints its values when the process is suspended and doesn't print anything when the process completes. Bruce 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?200204081320.g38DK2v09056>