On 10/30/15 3:34 PM, Stefan Tauner wrote:
> On Fri, 30 Oct 2015 14:00:10 -0400
> Chet Ramey wrote:
>
>> On 10/30/15 12:50 PM, Mike Frysinger wrote:
>>> On 26 Oct 2015 16:59, Stefan Tauner wrote:
I was creating some exercises for my students when I noticed very
strange behavior of the t
On Fri, 30 Oct 2015 14:00:10 -0400
Chet Ramey wrote:
> On 10/30/15 12:50 PM, Mike Frysinger wrote:
> > On 26 Oct 2015 16:59, Stefan Tauner wrote:
> >> I was creating some exercises for my students when I noticed very
> >> strange behavior of the time built-in when sending SIGSTOP to a timed
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/30/15 12:50 PM, Mike Frysinger wrote:
> On 26 Oct 2015 16:59, Stefan Tauner wrote:
>> I was creating some exercises for my students when I noticed very
>> strange behavior of the time built-in when sending SIGSTOP to a timed
>> command interactiv
On 26 Oct 2015 16:59, Stefan Tauner wrote:
> I was creating some exercises for my students when I noticed very
> strange behavior of the time built-in when sending SIGSTOP to a timed
> command interactively (via ^Z):
you could always install the dedicated time program and then do:
$ /usr/bin/time
On 10/26/15 11:59 AM, Stefan Tauner wrote:
> Hi,
>
> I was creating some exercises for my students when I noticed very
> strange behavior of the time built-in when sending SIGSTOP to a timed
> command interactively (via ^Z):
>
> $ time sleep 5
> ^Z
> [1]+ Stopped sleep 5
>
> rea
Hi,
I was creating some exercises for my students when I noticed very
strange behavior of the time built-in when sending SIGSTOP to a timed
command interactively (via ^Z):
$ time sleep 5
^Z
[1]+ Stopped sleep 5
real0m0.880s
user0m0.002s
sys 0m0.000s
$ ps Tf
PID TTY
