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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
From the current output I would think the answer is already obvious, the one with a min/max depth stops at the first level after /home/*/mail and then you get a total of that, whereas the other find
works its way down to a single file level and provides the information back, some of these files may never be found if first level after mail does not hold true to the mtime used in first example.
Of course, I could be wrong, but that is what I see
What's strange though is the fact that the find that stops at the first level yields 1.1GB, whereas the unlimited find only comes up with 200MB. Had it been the opposite, it would have been a clear cut case for me.
Another difference: The unlimited find only looks at regular files. But can there be 900MB of directories and symbolic links?
hmmm ... I see where you are coming from, however, if the directory in the second command, where there is no restriction on file, could easily contain more than files matching the criteria add up to.
My thinking is that whilst the directory now matches the mtime, there may be little to no actual files that do, so the first find would not have gone there.