Does the /data/test directory exist prior to execution? Otherwise cp is
just copying the result set one at a time to a regular file at /data/test.
You may want to append a forward slash to the directory name, as that will
cause cp to error if the directory doesn't exist instead. Or chain the
com
Stephane Chazelas wrote:
2016-02-25 03:03:41 -0800, Linda Walsh:
Stephane Chazelas wrote:
$ time bash -c 'while ((SECONDS < 1)); do :; done'
bash -c 'while ((SECONDS < 1)); do :; done' 0.39s user 0.00s system 99% cpu
0.387 total
Sorry I took "cpu xxx total" to be th
2016-02-25 10:48:51 -0500, Chet Ramey:
[...]
> Because bash doesn't have floating point arithmetic.
Yes, makes sense. mksh having $EPOCHREALTIME floating point even
though it doesn't have floating point arithmetic does sound
weird.
Any plan of adding floating point arithmetic support to bash by
t
On 2/25/16 8:18 AM, Stephane Chazelas wrote:
> Similar features would be welcome in bash.
>
> bash has "times" that gives you CPU time with sub-second
> granularity. It's got a "printf %T" a la ksh93, but no %N, its
> $SECOND is only integer (and currently has that issue discussed
> here).
Becau
On 2/25/16 8:34 AM, Michael Felt wrote:
> AIX is "no more entitled" to it, but they are using it - and "it" is
> stopping make from succeeding.
You're still using the version of bash that you reported on originally.
Try the just-released bash-4.4-rc1 instead.
--
``The lyf so short, the craft so
2016-02-25 13:18:17 +, Stephane Chazelas:
[...]
> > function __age { declare ns=$(date +"%N"); declare -i
> > ms=${ns##+(0)}/100;
> > printf "%4d.%03d\n" $SECONDS $ms
> > }
> [...]
>
> I'm not sure how that gives you the time since startup.
> Currently, if bash is started at
>
> 00:00:00
AIX is "no more entitled" to it, but they are using it - and "it" is
stopping make from succeeding.
+ > .buildaix/make.out
../src/bash-4.4/parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr]
"../src/bash-4.4/execute_cmd.c", line 4655.16: 1506-068 (W) Operation
between types "struct array*"
2016-02-25 03:03:41 -0800, Linda Walsh:
> Stephane Chazelas wrote:
> >$ time bash -c 'while ((SECONDS < 1)); do :; done'
> >bash -c 'while ((SECONDS < 1)); do :; done' 0.39s user 0.00s system 99% cpu
> >0.387 total
> >
> >That can take in between 0 and 1 seconds. Or in other words,
> >$SECONDS b
Stephane Chazelas wrote:
$ time bash -c 'while ((SECONDS < 1)); do :; done'
bash -c 'while ((SECONDS < 1)); do :; done' 0.39s user 0.00s system 99% cpu
0.387 total
That can take in between 0 and 1 seconds. Or in other words,
$SECONDS becomes 1 in between 0 and 1 second after the shell was
st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jaboatão dos Guararapes, Pernambuco, Brazil, 25 February 2016.
Subject: Translation of the Bash Reference Manual - edition 4.3 -
version 4.3, 2 February 2014, into Brazilian Portuguese language
[ANNOUNCEM
10 matches
Mail list logo
