<div>I don't remember if I've run into that specifically, but I remember a similar situation where I would do an md5sum of the file in the destination directory to check if both files were the same, avoiding the need for the move. If they didn't have the same hash, I would unlink the file in the destination directory before doing the move.</div>
<br><div class="gmail_quote">On Sat, Jan 15, 2011 at 1:29 PM, <span dir="ltr"><<a href="mailto:arocker@vex.net">arocker@vex.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
I seem to have encountered a strange problem with Perl's "move" command<br>
(from File::Copy). (The qualification is due to the fact that I have not<br>
directly observed the facts, only had them reported to me.)<br>
<br>
When move is used to transfer a file from one directory to another (empty)<br>
one, everything behaves as advertised. File appears in destination,<br>
disappears from source.<br>
<br>
If the file already exists in the destination directory, (a legitimate<br>
situation for this program), the original does not get deleted, but the<br>
move appears to have returned a "true" value. (I check it).<br>
<br>
I can't report many of the facts one would usually seek in such a case,<br>
such as permissions and ownerships, because I don't have access to the<br>
testing machine.<br>
<br>
Despite all the above hand-waving, has anybody encountered a problem like<br>
this?<br>
<br>
_______________________________________________<br>
toronto-pm mailing list<br>
<a href="mailto:toronto-pm@pm.org">toronto-pm@pm.org</a><br>
<a href="http://mail.pm.org/mailman/listinfo/toronto-pm" target="_blank">http://mail.pm.org/mailman/listinfo/toronto-pm</a><br>
</blockquote></div><br>