New answers tagged debugging
I ran these commands to get nginx back up and working: # remove nginx conf files apt-get purge nginx # reinstall apt-get install nginx # make sure the default site is enabled ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default # start nginx sudo /etc/init.d/nginx start nginx is now working!!
Indeed, as @zongfu pointed out, find does not cache its results in a file, but rather the kernel is caching the directories find is reading so they can be read again without touching the disk, which is why it is faster. If you still want to see what kind of IO a program is doing though, you can use strace. This program runs another program you specify and ...
find does not cache anything, especially onto disk. The reason why the second run is a lot faster is because the Linux caches the accessed data (in this case directory listings) in memory (see free).
Top 50 recent answers are included