Birmingham mumbai

[
 193 
]
The output of 
du -h
 can often be more verbose than you actually need in order to 
pinpoint your culprit
 and can fill several screens. To simplify it, my favorite variation 
of this command is the following:
du -hsc * 
Basically, you would run 
du -hsc *
 within a directory that's as close as possible 
to where you think the problem is. The 
-h
 option, as we know, gives us human-
readable output (essentially, giving us output in the form of megabytes, gigabytes, 
and so on). The 
-s
 option gives us a summary and 
-c
 provides us with the total 
amount of space used within our current working directory. The following 
screenshot shows this output from my laptop:
Figure 8.3: Example output from du -hsc *
The 
du
 command is only able to scan directories that its calling 
user has permission to scan. If you run this as a non-root user, then 
you may not be getting the full picture. Also, the more files and 
sub-directories that are within your current working directory, 
the longer this command will take to execute. If you have an idea 
where the resource hog might be, try to 
cd
 into a directory further 
in the tree to narrow your search down and reduce the amount of 
time the command will take.

---

Monitoring System Resources