Re^2: If I had a Free Two Months...

Why didn't you use File::Find? That solves the infinite loop problem which you've ignored. It works the same as yours except its less buggy and uses system() with distinct arguments to avoid accidental shell processing.

#!perl -w
use strict;
use File::Find;

my $start_dir = shift;
find( sub { system @ARGV if -d }, $start_dir );
[download]

Comment on Re^2: If I had a Free Two Months... Download Code

Replies are listed 'Best First'.
Re^3: If I had a Free Two Months... by kelan (Deacon) on Jun 22, 2005 at 17:12 UTC
I knew someone would ask:) I've never used File::Find, which is why I didn't. I don't have much need for recursively processing directories. My post was mostly about showing that it wouldn't take two months to write something similar, rather than present a full solution. I used `system` that way on purpose, so that it would go through shell processing. The OP specifically mentioned wanting to send shell commands through, and those probably would be more useful if the shell got to process them.	[reply]
Re^4: If I had a Free Two Months... by diotalevi (Canon) on Jun 22, 2005 at 17:17 UTC
Oh oh. Here's the same non-buggy version that does invoke the shell. To fix the bug in your code, you'll need to follow symlinks and whenever considering entering a directory, decide whether you've been there before. Symlinks will cause your existing code to enter infinite loops and to run the command on some things more than once. `#!perl -w use strict; use File::Find; my ( $start_dir, $command ) = @ARGV; find( sub { system $command if -d }, $start_dir );` [download]	[reply] [d/l]
Re^5: If I had a Free Two Months... by samizdat (Vicar) on Jun 23, 2005 at 16:51 UTC
See? Thanks to PM, I know have my whole 2 months back. Awesome, diotalevi, and also kudos to those who've pointed out how to use NIX find*! :D	[reply]