Date: Fri, 7 Jun 2002 09:16:14 -0700 (PDT) From: Ross Lippert <ripper@eskimo.com> To: bradyn@maths.tcd.ie Cc: pepper@rockefeller.edu, freebsd-docs@FreeBSD.ORG Subject: Re: docs/38985: time doesn't recognize its command-line options Message-ID: <200206071616.JAA13829@eskimo.com> In-Reply-To: <200206071702.aa68738@salmon.maths.tcd.ie> (message from Niall Brady on Fri, 07 Jun 2002 17:02:32 %2B0100)
next in thread | previous in thread | raw e-mail | index | archive | help
>Sounds like you're using the shell built-in version of time...
>try doing
> which time
>to see which one you're using. /usr/bin/time supports the flags
>you mentioned!
HAHA!! not so fast there buddy.
bash-2.05a$ which time
/usr/bin/time
bash-2.05a$ time date
Fri Jun 7 12:11:08 EDT 2002
real 0m0.003s
user 0m0.000s
sys 0m0.001s
bash-2.05a$ /usr/bin/time date
Fri Jun 7 12:11:12 EDT 2002
0.00 real 0.00 user 0.00 sys
bash-2.05a$ which which
/usr/bin/which
bash-2.05a$ /usr/bin/which time
/usr/bin/time
I get burned by this too. What is the RIGHT way to:
1) know if a particular function is being done by the shell or not
2) get a list of all commands the shell is doing for you which are also
are the names of exectuables in your current PATH.
-r
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200206071616.JAA13829>