what about a system call to mv?

Is there any reason (apart from platform dependencies) not to do this using

system "mv /dir/* /newdir/"
[download]

or somesuch similar thing? I doubt this would address the "moving to diff dirs on diff drives" issue-- I'm just curious if this is a workable solution. (being a lazy monk, I haven't monkeyed much with File::copy My knee jerk reaction in such a situation is to make the call, and portability be damned.)

The Autonomic Pilot; it's FunkyTown, babe.

Comment on what about a system call to mv? Select or Download Code

Replies are listed 'Best First'.
RE: what about a system call to mv? by davorg (Chancellor) on Jun 27, 2000 at 18:06 UTC
Well passing user input to `system` can always be a bit dodgy. You'd better be running that script in taint mode. -- <http://www.dave.org.uk> European Perl Conference - Sept 22/24 2000 <http://www.yapc.org/Europe/>	[reply]
RE: RE: what about a system call to mv? by KM (Priest) on Jun 27, 2000 at 18:11 UTC
Not just in taint mode, but properly untainting (see Untaint.pm, and perlsec), but also calling system in a safe way. Read perlsec (I wish it was named perlsex, since that is what I always seem to type) over to see how to safely make system() calls. Cheers, KM	[reply]