The two numbers between the ... represent values for "ru_utime" and
"ru_stime". The accounting values for ru_utime the days before the
"jump" are correct but afterwards they are nonsense for some days and
than ok again (this job was running with 100% cpu usage all the
time!). But all values for ru_stime are looking strange. Keep in mind:
1 day == 86400 sec.
In addition for all jobs showing this behaviour after 35793:37, the
values for the accumulated cpu-usage differ for every job:
[2012-05-29 05:18:32] 30591 ? R 10557290:44 ./fortran_kdis 2 27
[2012-05-29 05:34:42] 30636 ? R 11129626:19 ./fortran_kdis 2 31
[2012-05-29 05:58:20] 30637 ? R 12274089:59 ./fortran_kdis 2 30
[2012-05-29 06:02:37] 30630 ? R 12274256:17 ./fortran_kdis 2 28
[2012-05-29 06:03:12] 30634 ? R 11129641:38 ./fortran_kdis 2 29
[2012-05-29 06:09:44] 30638 ? R 12274280:17 ./fortran_kdis 2 32
[2012-05-29 06:23:55] 30587 ? R 11701990:44 ./fortran_kdis 2 26
Used kernel and architecture are:
# uname -a
Linux warg09 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux
Any help to get rid of this issue, would be highly appreciated.
Thanks in advance...
--
Uwe Bolick
Zentrum für Astronomie und Astrophysik
Technische Universität Berlin
EW 8-1, Hardenbergstr. 36, D-10623 Berlin (Germany)
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120917143547.GA15147@astro.physik.tu-berlin.de">http://lists.debian.org/20120917143547.GA15147@astro.physik.tu-berlin.de