top, state, find utility
find utility always starts in "D" state and may keep beeing in this state for as long as it wants(needs?). Could someone explain why. What I am doing is:
# find /(anything) -name ^regExpr(also might be a name*)
sometimes complemented with the "-d" option
Cpu(s): 3.0%us, 2.5%sy, 0.0%ni, 94.2%id, 0.3%wa, 0.0%hi, 0.0%si, 0.0%st
random ss of the top's cpu(s) during this "hang".
Also, the "1min load average" jumps from almost insignificantly to like 5.0. What is it waiting for? Why? My CPU doesn't let it be executed, no idea. Sorry if stupid.
Last edited by eeluve; 12-08-2012 at 03:10 AM.