I have tried both. For example, plink works just fine (from Windows) to copy a file from one location on the Linux server to another location on the same Linux server:
Here is a batch file that works: -------------------- @echo on path=\putty;%path% plink webxxx.webfaction.com -l webfactionlogin -pw 123456789abc -ssh -v -L 3001:localhost:3001 -m CopyCommands.txt -------------------- Here is what is in CopyCommands.txt -------------------- cp /home/webfactionlogin/webapps/app_one/file1.exe /home/webfactionlogin/webapps/app_two/. cp /home/webfactionlogin/webapps/app_one/file2.exe /home/webfactionlogin/webapps/app_two/. cp /home/webfactionlogin/webapps/app_one/file3.exe /home/webfactionlogin/webapps/app_two/. -------------------- I am certain that rsync is working correctly because after I put in the password it copies files correctly. The problem is how to automate passing the password. I got a return email from Webfaction support confirming that I have the correct location for the public key on their server but they don't know about where to put things on the windows workstation. ----- Original Message ----- From: "Ted Roche" <[email protected]> To: <[email protected]> Sent: Monday, June 14, 2010 10:46 AM Subject: Re: [NF] Webfaction web hosting notes On Mon, Jun 14, 2010 at 11:49 AM, <[email protected]> wrote: > > The attributes on the Linux server .ssh is 664 That looks a lot too permissive. You usually want your .ssh directory to be 700 - and files within that directory 0600 > rsync -av "/cygdrive/c/LocalWindowsFolder/" > "[email protected]:~/webapps/DestinationFolder" OK, that's telling rsync to archive files, but it doesn't know to use ssh. On Linux, I'd add the command option: --rsh='ssh' after the -av to tell it to use ssh as the remote shell. I've still not got sufficient information: are you using the executable ssh or Plink to try to make your connection? I'm afraid you might be crossing the beams here: I see you mentioning cygwin (an awesome POSIX emulator for the WinDOS platform, btw) and Putty. These are two different ways to implement functionality on Windows: cygwin creates a POSIX-like environment (and it looks like that's what you're trying to run the rsync command in) while PuTTY is a re-implementation of ssh on Windows. PuTTY doesn't do all the things ssh does in the way that ssh does them. For example, it stores its keys differently. Either PuTTY or cygwin plus ssh will work, but you shouldn't be mixing the two. Assuming you're using PuTTY and rsync (there are some promising Google hits on those keywords), let's take rsync out of the picture for a moment, and confirm you can connect from your Windows machine to your hosted machine using PuTTY. If not, focus on debugging that connectivity first, then we can introduce rsync into the mix. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/08a101cb0cc3$13e19ce0$7a00a...@w2k3s02 ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
