On Sun, Jun 13, 2010 at 1:56 PM, Ed Leafe <[email protected]> wrote: > On Jun 13, 2010, at 11:44 AM, <[email protected]> <[email protected]> > wrote: > > You need to set up public/private keys on the machines. If they are > present, rsync will use them to authenticate and will not need a password. > Google for "ssh-keygen" and I'm sure you'll find tons of information about > how to do this. >
I think this is only true if you are running rsync over ssh, which I would consider a best practice. I do something similar to this in uploading data from some of my clients to our in-house Linux systems. I think Kam has Windows in-house, so if he wants to use ssh, he's going to need to set up ssh on the Windows end. I recommend the PuTTY package of files to do this (PuTTY, Plink, Pagent and others). Essentially, you launch Pagent manually and supply a key on your Windows server so it can cache the ssh keys in memory. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ 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/[email protected] ** 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.
