2015-07-06 14:11 GMT+02:00 Rogério Brito <[email protected]>: > When I run cruft on my systems (various arches, including amd64 and armel, > for instance) with the following command line I get the errors listed below: > > # cruft -d / -d /boot -r report.log --ignore /home --ignore /var --ignore /tmp > /usr/lib/cruft/explain/USERS: 160: [: /usr/lib/cruft/cruft_find: unexpected > operator > /usr/lib/cruft/explain/USERS: 160: [: /usr/lib/cruft/cruft_find: unexpected > operator
This is due to this dumb copy-paste error I made while editing common.sh: https://github.com/a-detiste/cruft/commit/051f55eb17b1acb0e17463dbd8475706ef7c99f7 now fixed: https://github.com/a-detiste/cruft/commit/b38b19c74c3dd11812b2991dc04a8642395401c0. Can you please directly edit /usr/lib/cruft/common.sh and remove the extraneous "$@" to check that it solves your problem ? --- I see you are using "--ignore /home", which is what well everybody should do to avoid that /home got scanned *twice* only just to detect broken symlinks & non-owned files.(cruft computes a huge list with these items, another huge one without these items but well all regular files, the compare the two.) I was really tempted to make it the default behaviour, but I don't want to break users expectations either. It's not like I can send a survey to "registrated customers" to get a feeling of what they think about it. For cruft-ng (my rewrite of the shell/perl/c engine in C++); I just never scan further that the first level in /home; and avoid /tmp altogether. Well, speed was priority & command lines are not implemented at all at the moment, but the defaults are saner; and tool can be indirectly configured by tweaking mlocate's /etc/updatedb.conf . Greets, Alexandre -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
