(i) Right. My bad. I wrote mv but meant sftp (ii) Reasonable minds can differ on this one, but I still think you are better off in that case using scp or sftp and deleting afterwards. A "mv" is essentially: load to memory; write to destination; delete from origination; release memory. I'd be hesitant to do an automatic, transparent, immediate, remote delete over the wire. The server may have sent the file out the ethernet port, but that's no guarantee the client received and properly wrote the file. If you have mounted the remote file system under fuse, you would at least have fusefs to help ensure it all got done right. (Handling the reading, writing, and verifying of files a lot of what file systems are supposed to do.)
Thought: You could make ssh run an md5 hash at both ends to ensure everything was ducky before deleting the remote file. Of course, that would require rewriting both the client and the server. For upstream's view, see http://www.openssh.com/faq.html#2.10 Loye Young -- there is no 'move' equivalent for scp https://bugs.launchpad.net/bugs/92167 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
