Re: Not able to use native linux commands in a perl script

Special attention to the documents re File::Copy, highlighted by toolic!

There are -- occasionally -- valid reason for using shelling to system commands rather than using Perl functions (modules). What you've described is NOT one of them.

And, as others noted, we can't be much (reliable) help without knowing what your code looks like and what error message you're receiving.

Comment on Re: Not able to use native linux commands in a perl script

Replies are listed 'Best First'.
Re^2: Not able to use native linux commands in a perl script by JavaFan (Canon) on Dec 13, 2010 at 21:43 UTC
I find File::Copy an excellent reason to use `system`. Things I cannot do with File::Copy: Preserve the execute bit. Copy more than one file at a time. Recursively copy. Use any of the other arguments of `cp`. Use `scp` with a mostly similar syntax as `cp` for copying to different machines. Luckely the destructiveness doing of `File::Copy::copy("file1", "file2", "dir")` has been fixed in 5.12. I never use `File::Copy` anymore. I've spend way too much time fighting it. `system "cp"` never, ever surprises me, and always just works.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Not able to use native linux commands in a perl script
by JavaFan (Canon) on Dec 13, 2010 at 21:43 UTC

excellent

system

Preserve the execute bit.
Copy more than one file at a time.
Recursively copy.
Use any of the other arguments of cp.
Use scp with a mostly similar syntax as cp for copying to different machines.

File::Copy::copy("file1", "file2", "dir")

I never use File::Copy anymore. I've spend way too much time fighting it. system "cp" never, ever surprises me, and always just works.

[reply]
[d/l]
[select]