Tag Info

New answers tagged

1

Short answer: Yes, the files are safe to delete - they are basically just backups of previous cluster states. But... Long answer: The Policy Engine (the part of a Pacemaker cluster which decides what to do when something happens within the cluster) safes backups of the cluster state (configuration and state of resources) to /var/lib/pengine. These files are ...


0

What you should see is that in both cases you probably do not get the disk space usage of your pictures. If you have thousands of pictures, it probably on both cases exceed the limit for the exec call. Why? Well the -exec (...) + command adds parameters to the execvp system call. The man page defines the limit of its underlying system call as follow ...


3

The answers given until now do not take into account that the file list passed from find to du may be so long that find automatically splits the list into chunks, resulting in multiple occurences of total. You can either grep total (locale!) and sum up manually, or use a different command. AFAIK there are only two ways to get a grand total (in kilobytes) of ...


1

If the list of files is too big that it can't be passed to a single invocation of du -c, on a GNU system, you can do: find . -iname '*.jpg' -type f -printf '%b\t%D:%i\n' | sort -u | cut -f1 | paste -sd+ - | bc (size expressed in number of 512 byte blocks). Like du it tries to count hard links only once. If you don't care about hardlinks, you can ...


5

find ... -exec cmd {} + will execute cmd as many times as necessary so as not to break the limit of the size of the arguments passed to a command. When using find . -exec du {} +, the size of the file list is smaller than when using find verylongdirname -exec du {} +. So it's likely the find verylongdirname will run more du commands than the find . one. ...



Top 50 recent answers are included