Unfortunately, it looks as if bash doesn't have a "time" builtin (only a
"times" one), so this is - at best - only part of the problem. But
still, this builtin seems to be the cause here.
Perhaps reassign the bug to bash (since it is impossible to disable the
builtin interpretation of "time" since it isn't formally a builtin).
short summary:
(Shell used: bash from Debian Etch, preparation "enable -n times")
time -o /tmp/time_usage sleep 1 # fails
/usr/bin/time -o /tmp/time_usage sleep 1 # works
perl -e 'system("time","-o","/tmp/time_usage","sleep","1");' # works
So it isn't a problem within the time binary itself, but with bash here.
However "enable" (a builtin command in bash to enable/disable builtin
commands) doesn't list the "time" builtin. "enable time" reports there
isn't any such builtin, "enable -n times" disables the equivalent to
"time" that is a builtin, but "time" is still interpreted inside bash as
you can see from the above tests.
regards,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
