Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When i use the mv command it give me the same error
Code:
casper@casperbox:~$ ssh casper@192.168.81.95 "cp -fr /home/clearing.txt /home/casper/clearing/"
cp: `/home/clearing.txt' and `/home/casper/clearing/clearing.txt' are the same file
right now i am moving the file away and then copying it...
If this is a hard link then it is in fact "the same file" and there is no need to copy from one to the other.
Run "ls -l /home/casper/clearing/" if you see a number higher than 1 in the second column (between mode and owner) then the file is a hard link. If you run "ls -i" on both files they should show the same inode number if they are the same.
Are you doing this copy after updating /home/clearing.txt? If the other one is a hard link to this one then there is no reason to do the copy at all. Any changes to the first one are also changes to the second one as they ARE "the same file".
it is a file of the same name, however it is updated daily.
i am working on maybe getting some rsync going so I dont have to transfer the whole file just the changes.
until then I am using keyed ssh to mv the file, then copy the file.
You're not transferring a file with the above - you're ssh'ing into the other machine then doing a local copy on it.
You'd need to use scp rather than cp to "copy" from one machine to another. Of course you can also do rsync for such copies. If you type "man scp" and "man rsync" you can see options including those for overwriting if the file is already there. However, one of the main benefits of rsync is to only copy those things that don't already exist - thereby saving network bandwidth.
When i use the mv command it give me the same error
Code:
casper@casperbox:~$ ssh casper@172.29.81.95 "cp -fr /home/clearing.txt /home/casper/clearing/"
cp: `/home/clearing.txt' and `/home/casper/clearing/clearing.txt' are the same file
walt@walt-nasdaq:~$
right now i am moving the file away and then copying it...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.