On Mon, 2007-12-24 at 01:27 -0500, Matt McCutchen wrote:
> On Sun, 2007-12-23 at 15:55 -0500, Ming Zhang wrote:
> > if sender read by path again and get ENOENT, then this ENOENT can tell
> > rsync enough info. (though current rsync might say partial transfer
> > though it is a vanished file... )
>
bOn Mon, 2007-12-24 at 18:34 -0500, Eric S. Johansson wrote:
> I'd love for the remote backup to be encrypted locally so one could
> backup to a hostile host.
That limits your options. The main program I know of that can encrypt
backups before sending them is duplicity
( http://duplicity.nongnu.o
Matt McCutchen wrote:
- Are you backing up just your own laptop, or should the setup accommodate
multiple machines?
seems to me that the first is a subset of the latter
- Is it a priority to keep the client script simple?
it would be nice but hiding complexity behind a good ui is ok too.
On Wed, 2007-11-21 at 14:55 -0500, Eric S. Johansson wrote:
> Matt McCutchen wrote:
> > On Sun, 2007-11-18 at 17:45 -0500, Eric S. Johansson wrote:
> >> Using some of the techniques you show here, it would be possible to
> >> trigger the
> >> backup process and push the data from the laptop.
> >
Apparently the reverse resolving is always done, when a client connects
to an rsync daemon; this can be a problem with anonymous rsync access
where the whole world may connect but a large part of the world doesn't
have its reverse resolving working. In these cases you have to wait for
the DNS look
