Your message dated Sat, 8 Feb 2014 18:45:46 -0700
with message-id <[email protected]>
and subject line Re: Bug#388458: time: Time does not parse its parameters
has caused the Debian Bug report #388458,
regarding time: better shell built-in warning in man page
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
388458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388458
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: time
Version: 1.7-21
Severity: important
Time does not parse its own parameters and treats everything on the
command line like the program it should run and its parameters.
For example the following works:
jamborm@cetus:~/tmp/randwrite$ time bash < /dev/null
real 0m0.005s
user 0m0.000s
sys 0m0.004s
But this does not:
jamborm@cetus:~/tmp time -f "%e" bash < /dev/null
bash: -f: command not found
real 0m0.002s
user 0m0.000s
sys 0m0.000s
OTOH, I suspect this might be a bash issue because I have just found
out that /usr/bin/time works as expected.
TIA
Martin
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.14mj01
Locale: LANG=C, LC_CTYPE=cs_CZ (charmap=UTF-8) (ignored: LC_ALL set to
en_US.UTF-8)
Versions of packages time depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
time recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I have read through this bug log carefully and I believe that it can
be closed. A summary of the events of the bug log are:
Martin Jambor wrote:
> jamborm@cetus:~/tmp time -f "%e" bash < /dev/null
> bash: -f: command not found
Bas Kloet wrote:
> This is not a bug in the debian `time' program , but you get this
> problem when you use Bash (or another shells) built-in time command.
> Use /usr/bin/time and you will see that all works as expected.
Tollef Fog Heen wrote:
> reassign 388458 bash
Neil Moore wrote:
> ...explanations and descriptions concerning time keyward in bash...
Jonathan Nieder wrote:
> reassign 388458 time 1.7-21
> severity 388458 minor
> ...
> Reassigning to time, so the manual can be updated to warn that
> "time" must be quoted to avoid shells' builtin time commands.
Tollef Fog Heen wrote:
> It already does:
>
> 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
>
> (arguably, it shouldn't say «bash» there, but that's a really minor
> thing.)
And the man page does say this. Perhaps it should say this more
strongly in a WARNINGS section. I am thinking about it. But for the
purposes of this bug it is already there. :-)
Bob
signature.asc
Description: Digital signature
--- End Message ---
