Re: Re: finding top 10 largest files

Purists may want to use File::Find instead of find.

Also, people who don't like to write horrible crash-prone and security-holed scripts might like to use the -print0 action when backticking (or "open-to-pipe"ing) find commands, coupled, of course with local $/ = "\0";.

Oh, likewise, if you're finding into a xargs call... it's always a good idea to find ... -print0 | xargs -0 .... Anybody ever think that there should be a shellmonks?

------------
:Wq
Not an editor command: Wq
[download]

Comment on Re: Re: finding top 10 largest files Select or Download Code

Replies are listed 'Best First'.
Re: Re: Re: finding top 10 largest files by flyingmoose (Priest) on Feb 03, 2004 at 02:36 UTC
Though I doubt any one wants to be known as a shellmonk, it would be very useful to have a few pages of "now that you know it Perl, how do you do it the hard way", just as reference :) I don't know how many times I skip past a find or a grep and jump straight into Perl due to my general slackness and intolerance for the various idiosyncracies. I also find that slackness causing me to use 'slocate' instead of 'find', but that's impatience and thus is a virtue :) Let's face it though. Perl is just easier.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: finding top 10 largest files
by flyingmoose (Priest) on Feb 03, 2004 at 02:36 UTC

I don't know how many times I skip past a find or a grep and jump straight into Perl due to my general slackness and intolerance for the various idiosyncracies.

I also find that slackness causing me to use 'slocate' instead of 'find', but that's impatience and thus is a virtue :) Let's face it though. Perl is just easier.

[reply]