ok... I think I figured out why it's doing this, and I'm not sure
whether or not to treat this as a bug anymore.
Calling 'time' explicitly (i.e. /usr/bin/time [args]) does actually work
properly. For example, calling /usr/bin/time --version yields:
GNU time 1.7
Apparently 'bash' has a built-in command called 'time' that serves a similar
purpose, and I didn't see it my first read-through, but the man-page actually
mentions this caveat:
-----------------------
Users of the bash shell need to use an explicit path in order to run
the external time command and not the shell builtin variant. On system
where time is installed in /usr/bin, the first example would become
/usr/bin/time wc /etc/hosts
-----------------------
I still feel this is is an issue, but unless we could disable/override the bash
builtin, i don't see how.
--
time command doesnt recognize it's own arguments
https://bugs.launchpad.net/bugs/660655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
