Subject: weird time(1) behaviour
To: None <>
From: Thomas Klausner <>
List: current-users
Date: 09/30/2007 21:15:01

I tried to time a long-running operation today on
NetBSD-4.99.31/amd64. In the middle I statused it (CTRL-T),
interrupted it (CTRL-Z) and then timed it again when I put it in the
foreground again. The output was like this:

# time longcmd
load: 2.86  cmd: longcmd 29364 [runnable] 2952.86u 126.60s 96% 104136k
[1]+  Stopped                 longcmd

real    75m15.099s
user    0m0.000s
sys     0m0.001s
# time fg

real    4m35.770s
user    69m18.580s
sys     2m51.754s

Why is the user/system time in the first time(1) output 0, and the
second time(1) output has the correct date for the complete runtime
(at least I guess it has)?