This question arises out of another post I made on the Newbie forum at http://www.linuxquestions.org/questi...d.php?t=587049

Something is overriding my time command. If I run it by a full path command /usr/bin/time, then all of it's options work as described in the man page. If I don't give it the full path though, then most of the arguments don't work and BASH tries to interpret them as separate commands (which error out because "-o", "-v", etc. aren't valid commands).
I've checked all of the usual suspects that I thought might cause a command to be altered but none of them turned up anything:
/root/.bashrc
/etc/bashrc
/etc/profile
The BASH man page - in case BASH had a built-in time command that was superceding the separate binary. (It didn't.)
I also checked my $PATH statement but didn't find a time command anywhere other than in /usr/bin/.

I can work around it just by giving it the full path, but I'd really like to know where/how this is happening.

Thanks in advance for any ideas you may have.

Wingnut

It's a shell internal command in bash. From the bash manual page:
I didn't find this yesterday when I read the other thread, but today I did... the bash manual page is a bit of a pain in the format of a single document, but the content is golden.

I looked through the bash man page three times before posting this and didn't find that! Guess I was looking more for a separate Time command definition sticking out on the left edge like the other bash commands have had (for, case, if, while, etc.).

Thanks again!

heh, that's exactly what I was looking for when I couldn't find it, using the less command: