David Lang a écrit :
On Sat, 3 Mar 2007, Eric Dumazet wrote:
# time ldd -r ./groff
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xf7e8f000)
libm.so.6 => /lib/tls/libm.so.6 (0xf7e6d000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7e62000)
libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xf7f4c000)
0.00user 0.00system 0:00.00elapsed 50%CPU (0avgtext+0avgdata
0maxresident)k
0inputs+0outputs (0major+777minor)pagefaults 0swaps
You can see 777 pagefaults instead of 696 on this example.
the version of time on my system (debian 3.1) doesn't give me the cpu or
pagefault info, just the times. where should I get the version that
gives more info? (although I don't think I can apply it directly to my
troubleshooting as the work is all being done in child processes).
time is a shell builtin.
But there is normally an /usr/bin/time standalone program.
# type time
time is a shell keyword
# time date
Sun Mar 4 12:15:54 CET 2007
real 0m0.003s
user 0m0.000s
sys 0m0.000s
# /usr/bin/time date
Sun Mar 4 12:15:56 CET 2007
0.00user 0.00system 0:00.00elapsed ?%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (0major+192minor)pagefaults 0swaps
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
