Limiting the files found to only files starting with st* is alot faster, due to a smaller list size.
After changing the find line to:
Its printing (almost) the same stats in quite near range (imo, regarding the task done)....
Only value changed is 'blank lines', raised from ~200 to ~1800.
Eventhough i've (theoreticly) removed more image files - which shouldnt contain empty lines anyway....
I wonder if you want to skip .git directories.
Then a -prune in find is more efficient.
Also it is more efficient to run the find once, and count the FILES in the loop.
NB the -print is needed: by explicitly printing the files it will not print the pruned directories.
This User Gave Thanks to MadeInGermany For This Post:
I have a project tree like that.
after running find command with the -no -empty option, i am able to have a list of non empty directory
DO_MY_SEARCH="find . -type d -not -empty -print0"
MY_EXCLUDE_DIR1=" -e NOT_IN_USE -e RTMAP -e NOT_USEFULL "
echo " " > $MY_TEMP_RESULT_1
while... (2 Replies)
A new project was posted on your project board.
Project title: Bash Shell Tutoring
Linux, Bash, Shell, UNIX
I work as a datawarehouse designer and developer.
Although I usually stick to the role of an analyst,... (0 Replies)
i have two doubts..
1. what is the use /etc/project file. i renamed this file and when i tried to switch user or login with some user account the login was happening slowly. but when i renamed it to original name it was working fine... why so?
2. unix already has useradd and grouadd for... (4 Replies)
We have a system running ssh. When a user logs in, they do not get the project they are assigned to (they run under "system"). I verify the project using the command "ps -e -o user,pid,ppid,args,project". If you do a "su - username", the user does get the project they are assigned to (and all... (2 Replies)