Pathologically Eclectic Rubbish Lister | |
PerlMonks |
Limitations to chmod and performanceby stefan k (Curate) |
on Nov 12, 2001 at 16:46 UTC ( [id://124815]=perlquestion: print w/replies, xml ) | Need Help?? |
stefan k has asked for the wisdom of the Perl Monks concerning the following question:
Fellow Monks, my SysAd is in the process of writing a permission-fix-a-scripttm. and he is going to do that in perl (thereby replacing the old and ugly shell script). Since there is a lot of files to check (several GB) this should be as rock-solid as possible and as fast as possible.
He uses File::Find, of course :-). One question that arose is whether it would be better to create a giant list of files and pass them to the chmod command and rely on it's implementation or to call chmod for every single file. (Probably the middle-solution of creating groups of a certain size himself is stoopid). This is the question of performance. The second question is whether chmod has a limit. Is there a maximum number of files/dirs that you can pass to chmod? Well, and since this seems to be a quite common problem I may add to his questions whether this not already exists somewhere (permission fixing system, including exception lists, group settings and more). A quick search in the Monastery yielded no perfect results for me.
Back to
Seekers of Perl Wisdom
|
|