| 1 |
On Mon, 2008-09-15 at 16:41 +0200, Alan McKinnon wrote: |
| 2 |
> On Monday 15 September 2008 16:31:45 Michael Sullivan wrote: |
| 3 |
> > On Mon, 2008-09-15 at 16:17 +0200, Alan McKinnon wrote: |
| 4 |
> > > On Monday 15 September 2008 16:09:42 Michael Sullivan wrote: |
| 5 |
> > > > Is there a way to do this? The problem with my |
| 6 |
> > > > theories on how to do this fall apart when I get to the part where a |
| 7 |
> > > > password has to be entered for rsync/scp. |
| 8 |
> > > |
| 9 |
> > > ssh keys. |
| 10 |
> > > |
| 11 |
> > > To avoid running more than one sync at a time, have the clients pull the |
| 12 |
> > > tree from the server in a cron spaced 30 minutes or an hour apart. Make |
| 13 |
> > > sure you pull the entire tree, and if you use eix to run update-eix |
| 14 |
> > > afterwards on the clients |
| 15 |
> > |
| 16 |
> > Create ssh keys without passphrases? That's not recommended... |
| 17 |
> |
| 18 |
> True, but it's infinitely better than a passwordless account. You did say that |
| 19 |
> you want an automated rsync/scp solution, that precludes setting up an rsync |
| 20 |
> server. I don't see that any other realistic options exist. |
| 21 |
> |
| 22 |
|
| 23 |
I just wanted to make sure that I understood correctly. I'll try to set |
| 24 |
something like that up today. Thank you for your help. :) |
Archives