Elijah has asked for the wisdom of the Perl Monks concerning the following question:
The file untars correctly but when I try to copy it over I get an error saying the file does not exist. Of course I then check the untarred directory and there the files are. I have checked file paths and they are correct, file permissions are correct, and I have even changed directory to the untarred directory and tried that. Still no go.
What I think may be happening is that the File::Copy is trying to copy over the file before it actually shows up from the untar process. Is there anyway I can prove this is what is happening? Also more importantly if this is the case how can I slow the script down and wait for it to show up before trying to copy it without implementing some kind of endless loop checking for it?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Archive::Tar then File::Copy?
by talexb (Chancellor) on Mar 15, 2005 at 18:51 UTC | |
|
Re: Archive::Tar then File::Copy?
by talexb (Chancellor) on Mar 15, 2005 at 18:54 UTC | |
| |
|
Re: Archive::Tar then File::Copy?
by ambrus (Abbot) on Mar 15, 2005 at 21:43 UTC | |
by Elijah (Hermit) on Mar 15, 2005 at 21:50 UTC | |
by Tanktalus (Canon) on Mar 15, 2005 at 21:54 UTC | |
|