Coming back to this in case anyone else runs into this issue. bash has a built in "time" command. But there is also a system time binary. The manual describes the system binary functionality only. So it's not really a bug so much that it's unexpected for the user. When you run bash in posix mode, it does use the time binary on the system.
If you start your shell with `bash --posix` or `sh` or `dash` the time command works as documented in the manual. If you're writing a shell script, using the standard `#!/bin/sh` should ensure your script follows the posix standard for time. You can also create an alias using `alias time=/usr/bin/time` which will override bash's internal time function for the system installed time binary. This issue is unlikely to ever be fixed as it's not really a bug, just unexpected behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/660655 Title: time command doesnt recognize it's own arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/time/+bug/660655/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
