UNIX for Dummies Questions & Answers

I would just use

find / -mtime +1 -print

and most versions of find these days will allow you to leave off the -print. The "-name \*" will cause find to ignore files that start with a dot which (I think) is not what the OP wanted. The "-exec echo {} \;" will mostly do the same thing as -print. But it invokes one process for every file. And if you have weird filenames, like "-n" it may or may not print them depending on your version of echo.

Thanks alot

I was just wondering.... I tried the sort version before and it worked fine, but I was trying to understand all the rest.
What does the error means by the way? Is that exec does not work with ; or something?

Thanks alot 4 your help.

Perderabo,

Thanks for that. I didn't realise that the `-exec ...` caused extra processes to be created to perform the `echo`, or the full extent of the `\*`.

Learn something new every day.
Thanks again

Although you did not need an -exec in this case, many times you will. The problem was lack of space delimiters. You tried:

# find / -mtime +1 -exec echo{}\;

It did not see the semicolon because it needs a space prior to backslash. Also, Cameron's entry had no space after echo, and for me that caused nothing to print. Add those spaces, and it should work:

# find / -mtime +1 -exec echo {} \;

Spot on Jimbo.
I didn't spot the lack of space in my initial posting.
Thanks for that