setting to invalid since there is essentially nothing to fix.
** Changed in: bash (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/356624
Title:
`time` cra
This is because bash's time is a keyword, not a builtin command ('type
time' will show). Therefore it will only be recognized if it is in the
input literally and unquoted.
--
`time` crashes in a script
https://bugs.launchpad.net/bugs/356624
You received this bug notification because you are a mem
Talked about this on irc and Pici noted something:
Its just using the default time output format, instead of the one that
it regularly uses. The manpage says that it should use the following
format if none is specified:
%Uuser %Ssystem %Eelapsed %PCPU (%Xtext+%Ddata %Mmax)k
%Iinputs+%Ooutputs (%F
i...@ikt-desk:~$ cmd="time ls"; $cmd
Dropbox Music Templates
0.00user 0.00system 0:00.00elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+305minor)pagefaults 0swaps
i...@ikt-desk:~$ uname -a
Linux ikt-desk 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:0
** Package changed: ubuntu => bash (Ubuntu)
--
`time` crashes in a script
https://bugs.launchpad.net/bugs/356624
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.ubun
