12 # can't say 'opendir my $dh, $dirname'
13 # need to initialise $dh
19 use vars qw($VERSION @ISA @EXPORT @EXPORT_OK);
22 @EXPORT = qw(mkpath rmtree);
23 @EXPORT_OK = qw(make_path remove_tree);
25 my $Is_VMS = $^O eq 'VMS';
26 my $Is_MacOS = $^O eq 'MacOS';
28 # These OSes complain if you want to remove a file that you have no
29 # write permission to:
30 my $Force_Writeable = grep {$^O eq $_} qw(amigaos dos epoc MSWin32 MacOS os2);
48 $object = '' unless defined $object;
49 $message .= ": $!" if $!;
50 push @{${$arg->{error}}}, {$object => $message};
53 _carp(defined($object) ? "$message for $object: $!" : "$message: $!");
58 push @_, {} unless @_ and UNIVERSAL::isa($_[-1],'HASH');
63 my $old_style = !(@_ and UNIVERSAL::isa($_[-1],'HASH'));
70 ($paths, $verbose, $mode) = @_;
71 $paths = [$paths] unless UNIVERSAL::isa($paths,'ARRAY');
72 $arg->{verbose} = $verbose;
73 $arg->{mode} = defined $mode ? $mode : 0777;
77 $arg->{mode} = delete $arg->{mask} if exists $arg->{mask};
78 $arg->{mode} = 0777 unless exists $arg->{mode};
79 ${$arg->{error}} = [] if exists $arg->{error};
82 return _mkpath($arg, $paths);
90 foreach $path (@$paths) {
91 next unless defined($path) and length($path);
92 $path .= '/' if $^O eq 'os2' and $path =~ /^\w:\z/s; # feature of CRT
93 # Logic wants Unix paths, so go with the flow.
96 $path = VMS::Filespec::unixify($path);
99 my $parent = File::Basename::dirname($path);
100 unless (-d $parent or $path eq $parent) {
101 push(@created,_mkpath($arg, [$parent]));
103 print "mkdir $path\n" if $arg->{verbose};
104 if (mkdir($path,$arg->{mode})) {
105 push(@created, $path);
109 my ($e, $e1) = ($save_bang, $^E);
110 $e .= "; $e1" if $e ne $e1;
111 # allow for another process to have created it meanwhile
115 push @{${$arg->{error}}}, {$path => $e};
118 _croak("mkdir $path: $e");
127 push @_, {} unless @_ and UNIVERSAL::isa($_[-1],'HASH');
132 my $old_style = !(@_ and UNIVERSAL::isa($_[-1],'HASH'));
138 my ($verbose, $safe);
139 ($paths, $verbose, $safe) = @_;
140 $arg->{verbose} = $verbose;
141 $arg->{safe} = defined $safe ? $safe : 0;
143 if (defined($paths) and length($paths)) {
144 $paths = [$paths] unless UNIVERSAL::isa($paths,'ARRAY');
147 _carp ("No root path(s) specified\n");
153 ${$arg->{error}} = [] if exists $arg->{error};
154 ${$arg->{result}} = [] if exists $arg->{result};
162 $arg->{cwd} = getcwd() or do {
163 _error($arg, "cannot fetch initial working directory");
166 for ($arg->{cwd}) { /\A(.*)\Z/; $_ = $1 } # untaint
168 for my $p (@$paths) {
170 $p = ":$p" unless $p =~ /:/;
171 $p .= ":" unless $p =~ /:\z/;
173 elsif ($^O eq 'MSWin32') {
179 push @clean_path, $p;
182 @{$arg}{qw(device inode perm)} = (lstat $arg->{cwd})[0,1] or do {
183 _error($arg, "cannot stat initial working directory", $arg->{cwd});
187 return _rmtree($arg, \@clean_path);
195 my $curdir = File::Spec->curdir();
196 my $updir = File::Spec->updir();
200 foreach $root (@$paths) {
201 # since we chdir into each directory, it may not be obvious
202 # to figure out where we are if we generate a message about
203 # a file name. We therefore construct a semi-canonical
204 # filename, anchored from the directory being unlinked (as
205 # opposed to being truly canonical, anchored from the root (/).
207 my $canon = $arg->{prefix}
208 ? File::Spec->catfile($arg->{prefix}, $root)
212 my ($ldev, $lino, $perm) = (lstat $root)[0,1,2] or next ROOT_DIR;
215 $root = VMS::Filespec::pathify($root) if $Is_VMS;
217 # see if we can escalate privileges to get in
218 # (e.g. funny protection mask such as -w- instead of rwx)
220 my $nperm = $perm | 0700;
221 if (!($arg->{safe} or $nperm == $perm or chmod($nperm, $root))) {
222 _error($arg, "cannot make child directory read-write-exec", $canon);
225 elsif (!chdir($root)) {
226 _error($arg, "cannot chdir to child", $canon);
231 my ($cur_dev, $cur_inode, $perm) = (stat $curdir)[0,1,2] or do {
232 _error($arg, "cannot stat current working directory", $canon);
236 ($ldev eq $cur_dev and $lino eq $cur_inode)
237 or _croak("directory $canon changed before chdir, expected dev=$ldev ino=$lino, actual dev=$cur_dev ino=$cur_inode, aborting.");
239 $perm &= 07777; # don't forget setuid, setgid, sticky bits
240 my $nperm = $perm | 0700;
242 # notabene: 0700 is for making readable in the first place,
243 # it's also intended to change it to writable in case we have
244 # to recurse in which case we are better than rm -rf for
245 # subtrees with strange permissions
247 if (!($arg->{safe} or $nperm == $perm or chmod($nperm, $curdir))) {
248 _error($arg, "cannot make directory read+writeable", $canon);
253 $d = gensym() if $] < 5.006;
254 if (!opendir $d, $curdir) {
255 _error($arg, "cannot opendir", $canon);
260 if (!defined ${"\cTAINT"} or ${"\cTAINT"}) {
261 # Blindly untaint dir names if taint mode is
262 # active, or any perl < 5.006
263 @files = map { /\A(.*)\z/s; $1 } readdir $d;
272 # Deleting large numbers of files from VMS Files-11
273 # filesystems is faster if done in reverse ASCIIbetical order.
274 # include '.' to '.;' from blead patch #31775
275 @files = map {$_ eq '.' ? '.;' : $_} reverse @files;
276 ($root = VMS::Filespec::unixify($root)) =~ s/\.dir\z//;
278 @files = grep {$_ ne $updir and $_ ne $curdir} @files;
281 # remove the contained files before the directory itself
283 @{$narg}{qw(device inode cwd prefix depth)}
284 = ($cur_dev, $cur_inode, $updir, $canon, $arg->{depth}+1);
285 $count += _rmtree($narg, \@files);
288 # restore directory permissions of required now (in case the rmdir
289 # below fails), while we are still in the directory and may do so
290 # without a race via '.'
291 if ($nperm != $perm and not chmod($perm, $curdir)) {
292 _error($arg, "cannot reset chmod", $canon);
295 # don't leave the client code in an unexpected directory
297 or _croak("cannot chdir to $arg->{cwd} from $canon: $!, aborting.");
299 # ensure that a chdir upwards didn't take us somewhere other
300 # than we expected (see CVE-2002-0435)
301 ($cur_dev, $cur_inode) = (stat $curdir)[0,1]
302 or _croak("cannot stat prior working directory $arg->{cwd}: $!, aborting.");
304 ($arg->{device} eq $cur_dev and $arg->{inode} eq $cur_inode)
305 or _croak("previous directory $arg->{cwd} changed before entering $canon, expected dev=$ldev ino=$lino, actual dev=$cur_dev ino=$cur_inode, aborting.");
307 if ($arg->{depth} or !$arg->{keep_root}) {
309 ($Is_VMS ? !&VMS::Filespec::candelete($root) : !-w $root)) {
310 print "skipped $root\n" if $arg->{verbose};
313 if ($Force_Writeable and !chmod $perm | 0700, $root) {
314 _error($arg, "cannot make directory writeable", $canon);
316 print "rmdir $root\n" if $arg->{verbose};
318 push @{${$arg->{result}}}, $root if $arg->{result};
322 _error($arg, "cannot remove directory", $canon);
323 if ($Force_Writeable && !chmod($perm, ($Is_VMS ? VMS::Filespec::fileify($root) : $root))
325 _error($arg, sprintf("cannot restore permissions to 0%o",$perm), $canon);
332 $root = VMS::Filespec::vmsify("./$root")
334 && !File::Spec->file_name_is_absolute($root)
335 && ($root !~ m/(?<!\^)[\]>]+/); # not already in VMS syntax
338 ($Is_VMS ? !&VMS::Filespec::candelete($root)
339 : !(-l $root || -w $root)))
341 print "skipped $root\n" if $arg->{verbose};
345 my $nperm = $perm & 07777 | 0600;
346 if ($Force_Writeable and $nperm != $perm and not chmod $nperm, $root) {
347 _error($arg, "cannot make file writeable", $canon);
349 print "unlink $canon\n" if $arg->{verbose};
350 # delete all versions under VMS
353 push @{${$arg->{result}}}, $root if $arg->{result};
356 _error($arg, "cannot unlink file", $canon);
357 $Force_Writeable and chmod($perm, $root) or
358 _error($arg, sprintf("cannot restore permissions to 0%o",$perm), $canon);
362 last unless $Is_VMS && lstat $root;
370 # fix up slashes and case on MSWin32 so that we can determine that
371 # c:\path\to\dir is underneath C:/Path/To
382 File::Path - Create or remove directory trees
386 This document describes version 2.07 of File::Path, released
391 use File::Path qw(make_path remove_tree);
393 make_path('foo/bar/baz', '/zug/zwang');
394 make_path('foo/bar/baz', '/zug/zwang', {
399 remove_tree('foo/bar/baz', '/zug/zwang');
400 remove_tree('foo/bar/baz', '/zug/zwang', {
402 error => \my $err_list,
405 # legacy (interface promoted before v2.00)
406 mkpath('/foo/bar/baz');
407 mkpath('/foo/bar/baz', 1, 0711);
408 mkpath(['/foo/bar/baz', 'blurfl/quux'], 1, 0711);
409 rmtree('foo/bar/baz', 1, 1);
410 rmtree(['foo/bar/baz', 'blurfl/quux'], 1, 1);
412 # legacy (interface promoted before v2.06)
413 mkpath('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });
414 rmtree('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });
418 This module provide a convenient way to create directories of
419 arbitrary depth and to delete an entire directory subtree from the
422 The following functions are provided:
426 =item make_path( $dir1, $dir2, .... )
428 =item make_path( $dir1, $dir2, ...., \%opts )
430 The C<make_path> function creates the given directories if they don't
431 exists before, much like the Unix command C<mkdir -p>.
433 The function accepts a list of directories to be created. Its
434 behaviour may be tuned by an optional hashref appearing as the last
435 parameter on the call.
437 The function returns the list of directories actually created during
438 the call; in scalar context the number of directories created.
440 The following keys are recognised in the option hash:
446 The numeric permissions mode to apply to each created directory
447 (defaults to 0777), to be modified by the current C<umask>. If the
448 directory already exists (and thus does not need to be created),
449 the permissions will not be modified.
451 C<mask> is recognised as an alias for this parameter.
453 =item verbose => $bool
455 If present, will cause C<make_path> to print the name of each directory
456 as it is created. By default nothing is printed.
460 If present, it should be a reference to a scalar.
461 This scalar will be made to reference an array, which will
462 be used to store any errors that are encountered. See the L</"ERROR
463 HANDLING"> section for more information.
465 If this parameter is not used, certain error conditions may raise
466 a fatal error that will cause the program will halt, unless trapped
473 =item mkpath( $dir, $verbose, $mode )
475 =item mkpath( [$dir1, $dir2,...], $verbose, $mode )
477 =item mkpath( $dir1, $dir2,..., \%opt )
479 The mkpath() function provide the legacy interface of make_path() with
480 a different interpretation of the arguments passed. The behaviour and
481 return value of the function is otherwise identical to make_path().
483 =item remove_tree( $dir1, $dir2, .... )
485 =item remove_tree( $dir1, $dir2, ...., \%opts )
487 The C<remove_tree> function deletes the given directories and any
488 files and subdirectories they might contain, much like the Unix
489 command C<rm -r> or C<del /s> on Windows.
491 The function accepts a list of directories to be
492 removed. Its behaviour may be tuned by an optional hashref
493 appearing as the last parameter on the call.
495 The functions returns the number of files successfully deleted.
497 The following keys are recognised in the option hash:
501 =item verbose => $bool
503 If present, will cause C<remove_tree> to print the name of each file as
504 it is unlinked. By default nothing is printed.
508 When set to a true value, will cause C<remove_tree> to skip the files
509 for which the process lacks the required privileges needed to delete
510 files, such as delete privileges on VMS. In other words, the code
511 will make no attempt to alter file permissions. Thus, if the process
512 is interrupted, no filesystem object will be left in a more
515 =item keep_root => $bool
517 When set to a true value, will cause all files and subdirectories
518 to be removed, except the initially specified directories. This comes
519 in handy when cleaning out an application's scratch directory.
521 remove_tree( '/tmp', {keep_root => 1} );
523 =item result => \$res
525 If present, it should be a reference to a scalar.
526 This scalar will be made to reference an array, which will
527 be used to store all files and directories unlinked
528 during the call. If nothing is unlinked, the array will be empty.
530 remove_tree( '/tmp', {result => \my $list} );
531 print "unlinked $_\n" for @$list;
533 This is a useful alternative to the C<verbose> key.
537 If present, it should be a reference to a scalar.
538 This scalar will be made to reference an array, which will
539 be used to store any errors that are encountered. See the L</"ERROR
540 HANDLING"> section for more information.
542 Removing things is a much more dangerous proposition than
543 creating things. As such, there are certain conditions that
544 C<remove_tree> may encounter that are so dangerous that the only
545 sane action left is to kill the program.
547 Use C<error> to trap all that is reasonable (problems with
548 permissions and the like), and let it die if things get out
549 of hand. This is the safest course of action.
555 =item rmtree( $dir, $verbose, $safe )
557 =item rmtree( [$dir1, $dir2,...], $verbose, $safe )
559 =item rmtree( $dir1, $dir2,..., \%opt )
561 The rmtree() function provide the legacy interface of remove_tree()
562 with a different interpretation of the arguments passed. The behaviour
563 and return value of the function is otherwise identical to
568 =head2 ERROR HANDLING
574 The following error handling mechanism is considered
575 experimental and is subject to change pending feedback from
580 If C<make_path> or C<remove_tree> encounter an error, a diagnostic
581 message will be printed to C<STDERR> via C<carp> (for non-fatal
582 errors), or via C<croak> (for fatal errors).
584 If this behaviour is not desirable, the C<error> attribute may be
585 used to hold a reference to a variable, which will be used to store
586 the diagnostics. The variable is made a reference to an array of hash
587 references. Each hash contain a single key/value pair where the key
588 is the name of the file, and the value is the error message (including
589 the contents of C<$!> when appropriate). If a general error is
590 encountered the diagnostic key will be empty.
592 An example usage looks like:
594 remove_tree( 'foo/bar', 'bar/rat', {error => \my $err} );
596 for my $diag (@$err) {
597 my ($file, $message) = %$diag;
599 print "general error: $message\n";
602 print "problem unlinking $file: $message\n";
607 print "No error encountered\n";
610 Note that if no errors are encountered, C<$err> will reference an
611 empty array. This means that C<$err> will always end up TRUE; so you
612 need to test C<@$err> to determine if errors occured.
616 C<File::Path> blindly exports C<mkpath> and C<rmtree> into the
617 current namespace. These days, this is considered bad style, but
618 to change it now would break too much code. Nonetheless, you are
619 invited to specify what it is you are expecting to use:
621 use File::Path 'rmtree';
623 The routines C<make_path> and C<remove_tree> are B<not> exported
624 by default. You must specify which ones you want to use.
626 use File::Path 'remove_tree';
628 Note that a side-effect of the above is that C<mkpath> and C<rmtree>
629 are no longer exported at all. This is due to the way the C<Exporter>
630 module works. If you are migrating a codebase to use the new
631 interface, you will have to list everything explicitly. But that's
632 just good practice anyway.
634 use File::Path qw(remove_tree rmtree);
636 =head3 SECURITY CONSIDERATIONS
638 There were race conditions 1.x implementations of File::Path's
639 C<rmtree> function (although sometimes patched depending on the OS
640 distribution or platform). The 2.0 version contains code to avoid the
641 problem mentioned in CVE-2002-0435.
643 See the following pages for more information:
645 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286905
646 http://www.nntp.perl.org/group/perl.perl5.porters/2005/01/msg97623.html
647 http://www.debian.org/security/2005/dsa-696
649 Additionally, unless the C<safe> parameter is set (or the
650 third parameter in the traditional interface is TRUE), should a
651 C<remove_tree> be interrupted, files that were originally in read-only
652 mode may now have their permissions set to a read-write (or "delete
657 FATAL errors will cause the program to halt (C<croak>), since the
658 problem is so severe that it would be dangerous to continue. (This
659 can always be trapped with C<eval>, but it's not a good idea. Under
660 the circumstances, dying is the best thing to do).
662 SEVERE errors may be trapped using the modern interface. If the
663 they are not trapped, or the old interface is used, such an error
664 will cause the program will halt.
666 All other errors may be trapped using the modern interface, otherwise
667 they will be C<carp>ed about. Program execution will not be halted.
671 =item mkdir [path]: [errmsg] (SEVERE)
673 C<make_path> was unable to create the path. Probably some sort of
674 permissions error at the point of departure, or insufficient resources
675 (such as free inodes on Unix).
677 =item No root path(s) specified
679 C<make_path> was not given any paths to create. This message is only
680 emitted if the routine is called with the traditional interface.
681 The modern interface will remain silent if given nothing to do.
683 =item No such file or directory
685 On Windows, if C<make_path> gives you this warning, it may mean that
686 you have exceeded your filesystem's maximum path length.
688 =item cannot fetch initial working directory: [errmsg]
690 C<remove_tree> attempted to determine the initial directory by calling
691 C<Cwd::getcwd>, but the call failed for some reason. No attempt
692 will be made to delete anything.
694 =item cannot stat initial working directory: [errmsg]
696 C<remove_tree> attempted to stat the initial directory (after having
697 successfully obtained its name via C<getcwd>), however, the call
698 failed for some reason. No attempt will be made to delete anything.
700 =item cannot chdir to [dir]: [errmsg]
702 C<remove_tree> attempted to set the working directory in order to
703 begin deleting the objects therein, but was unsuccessful. This is
704 usually a permissions issue. The routine will continue to delete
705 other things, but this directory will be left intact.
707 =item directory [dir] changed before chdir, expected dev=[n] ino=[n], actual dev=[n] ino=[n], aborting. (FATAL)
709 C<remove_tree> recorded the device and inode of a directory, and then
710 moved into it. It then performed a C<stat> on the current directory
711 and detected that the device and inode were no longer the same. As
712 this is at the heart of the race condition problem, the program
713 will die at this point.
715 =item cannot make directory [dir] read+writeable: [errmsg]
717 C<remove_tree> attempted to change the permissions on the current directory
718 to ensure that subsequent unlinkings would not run into problems,
719 but was unable to do so. The permissions remain as they were, and
720 the program will carry on, doing the best it can.
722 =item cannot read [dir]: [errmsg]
724 C<remove_tree> tried to read the contents of the directory in order
725 to acquire the names of the directory entries to be unlinked, but
726 was unsuccessful. This is usually a permissions issue. The
727 program will continue, but the files in this directory will remain
730 =item cannot reset chmod [dir]: [errmsg]
732 C<remove_tree>, after having deleted everything in a directory, attempted
733 to restore its permissions to the original state but failed. The
734 directory may wind up being left behind.
736 =item cannot chdir to [parent-dir] from [child-dir]: [errmsg], aborting. (FATAL)
738 C<remove_tree>, after having deleted everything and restored the permissions
739 of a directory, was unable to chdir back to the parent. The program
740 halts to avoid a race condition from occurring.
742 =item cannot stat prior working directory [dir]: [errmsg], aborting. (FATAL)
744 C<remove_tree> was unable to stat the parent directory after have returned
745 from the child. Since there is no way of knowing if we returned to
746 where we think we should be (by comparing device and inode) the only
747 way out is to C<croak>.
749 =item previous directory [parent-dir] changed before entering [child-dir], expected dev=[n] ino=[n], actual dev=[n] ino=[n], aborting. (FATAL)
751 When C<remove_tree> returned from deleting files in a child directory, a
752 check revealed that the parent directory it returned to wasn't the one
753 it started out from. This is considered a sign of malicious activity.
755 =item cannot make directory [dir] writeable: [errmsg]
757 Just before removing a directory (after having successfully removed
758 everything it contained), C<remove_tree> attempted to set the permissions
759 on the directory to ensure it could be removed and failed. Program
760 execution continues, but the directory may possibly not be deleted.
762 =item cannot remove directory [dir]: [errmsg]
764 C<remove_tree> attempted to remove a directory, but failed. This may because
765 some objects that were unable to be removed remain in the directory, or
766 a permissions issue. The directory will be left behind.
768 =item cannot restore permissions of [dir] to [0nnn]: [errmsg]
770 After having failed to remove a directory, C<remove_tree> was unable to
771 restore its permissions from a permissive state back to a possibly
772 more restrictive setting. (Permissions given in octal).
774 =item cannot make file [file] writeable: [errmsg]
776 C<remove_tree> attempted to force the permissions of a file to ensure it
777 could be deleted, but failed to do so. It will, however, still attempt
780 =item cannot unlink file [file]: [errmsg]
782 C<remove_tree> failed to remove a file. Probably a permissions issue.
784 =item cannot restore permissions of [file] to [0nnn]: [errmsg]
786 After having failed to remove a file, C<remove_tree> was also unable
787 to restore the permissions on the file to a possibly less permissive
788 setting. (Permissions given in octal).
800 Allows files and directories to be moved to the Trashcan/Recycle
801 Bin (where they may later be restored if necessary) if the operating
802 system supports such functionality. This feature may one day be
803 made available directly in C<File::Path>.
809 When removing directory trees, if you want to examine each file to
810 decide whether to delete it (and possibly leaving large swathes
811 alone), F<File::Find::Rule> offers a convenient and flexible approach
812 to examining directory trees.
818 Please report all bugs on the RT queue:
820 L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=File-Path>
822 =head1 ACKNOWLEDGEMENTS
824 Paul Szabo identified the race condition originally, and Brendan
825 O'Dea wrote an implementation for Debian that addressed the problem.
826 That code was used as a basis for the current code. Their efforts
827 are greatly appreciated.
829 Gisle Aas made a number of improvements to the documentation for
830 2.07 and his advice and assistance is also greatly appreciated.
834 Tim Bunce and Charles Bailey. Currently maintained by David Landgren
835 <F<david@landgren.net>>.
839 This module is copyright (C) Charles Bailey, Tim Bunce and
840 David Landgren 1995-2008. All rights reserved.
844 This library is free software; you can redistribute it and/or modify
845 it under the same terms as Perl itself.