Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
to find all my pictures that are over a year old, but i keep getting argument list too long. How can i view what all the results are, even if it just dumps it to a file that i have to open?
to find all my pictures that are over a year old, but i keep getting argument list too long. How can i view what all the results are, even if it just dumps it to a file that i have to open?
The problem is with the '*'. You not only don't need
it - it causes the problem because bash kindly expands
it for you. So find is (possibly?) fed a list of files
by bash, rather than iterating through a directory tree.
Imagine your "/photos" has 2000 jpgs and 500 subdirectories.
With the * what happens is that you're telling find to start
a search in 2500 locations. Hence the "argument list too long".
Have to say it is much faster than ls | grep. I tries testing it with /usr (keyword "gnome" in Ubuntu) and - what do you know - it took just a few seconds to complete compared with up to a minute with ls | grep.
FYI: locate is a db updated by the OS usually once a day (cron).
Doesn't exist on other *nixes afaik and may not always be up to date if your system has been shutdown for a while....
FYI: locate is a db updated by the OS usually once a day (cron).
Doesn't exist on other *nixes afaik and may not always be up to date if your system has been shutdown for a while....
I have located on a few machines and I have never known it to automatically update tho it would be very easy to do. I prefer manually running updatedb because it then doesn't throttle the hard drive while the server maybe dealing with other things.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.