Re^2: 'unlink' seems to not work correctly ...

[codeacrobat]

... or unlink on the fly, with the no_chdir option. With no_chdir $File::Find::name and $_ are equivalent.

find( {wanted => \&wanted, no_chdir=>1}, @directories );

sub wanted {
  my $wanted = -l && !-e;

  push @msgs, $_ and $counter++ if $wanted;

return if $param{test} or !$wanted;

  unlink or croak "Warning: couldn't unlink '$_' :$OS_ERROR\n";

return;
}

Update Refactored wanted function.

[merlyn]

That is, if you're willing to pay the performance penalty for no_chdir, and in this case, it seemed unwarranted, since the workaround was so easy.

[Anonymous Monk]

performance penalty?

[merlyn]

Yes, no_chdir means that find needs to keep readdirring and stating longer and longer paths, repeatedly traversing the parent directories. Real find, like the default File::Find, uses chdir to ensure that the readdir and stats traverse the minimal number of inodes.