Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I am trying to transfer data between 2 CentOS 6.6 computers through SSH without requiring password. I have successfully set up a keypair with no password and when I execute the below command on command-line interface, it totally worked:
I have asked a moderator to obfuscate the IP address in your first post for you.
I did, as a show of good will =}
In all honesty I don't think that (in this day) it makes a difference. Put a new machine w/ a public IP up and it
will be probed in under a minute anyway ...
I have asked a moderator to obfuscate the IP address in your first post for you.
Quote:
Originally Posted by Tinkster
I did, as a show of good will =}
In all honesty I don't think that (in this day) it makes a difference. Put a new machine w/ a public IP up and it
will be probed in under a minute anyway ...
Cheers,
Tink
Thank you very much, Habitual and Tinkster!
Quote:
Originally Posted by jailbait
Crontab has a different PATH than root or user. Try using the full path name when you execute rsync in crontab, for example:
Hey Steve, I have tried your solution but it did not work as well. By the way, I think the problem is somehow crontab cannot make a connection through SSH because when I added "rsync -av --delete /backup1/ /backup2/" (local backup on 1 computer) to crontab, it worked. Thank you for your help but I still need more help in this case.
Once again, thank you guys for your assistance,
- Minh.
Last edited by quickbeard; 06-12-2015 at 10:25 AM.
I have figured out the problem. It seems that CLI and crontab run on different environments, so crontab need to be told where the private key is. I simply added the location of private key on the command:
In all honesty I don't think that (in this day) it makes a difference. Put a new machine w/ a public IP up and it will be probed in under a minute anyway ...
Yes, this is true. I was hoping to impart to the OP a "best practice" that is usual with posting IPs on public forums. No need to add to the fray!
We wouldn't advertise we have a home security system, now would we?
who knows. xxx.yyy.20.209 (the original post IP) may not have even been "his" and if that's the case, he's smarter that I gave him credit for. No offense to quickbeard.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.