On Wed, 17 Aug 2005 21:54:45 -0800, Noah wrote:
> but I want to do something a little different. I want the machine that I am
> backing up to intiate the ssh connection to the server that is providing the
> backup space. I still want the rdiff-backup exchange to be handled by ssh.
First, let's
>
> After this has been set up, the rest should be easy:
> a. learn how to use rdiff-backup
> b. adjust BACKUPUSER's authorized_keys file, tightening
>up security, perhaps adjusting so that the relevant
>line looks somewhat like this (one long line):
>
> from="11.22.33.44",no-pty,no-por
Noah wrote:
this is syntax for running a remote command, right? that is _not_ what I am
attempting to do. I want to initiate the rdiff-backup command on the server
that is getting backed up.
Noah, this is NOT the syntax for running a remote command. At the risk
of repeating what I and others
On Thu, 18 Aug 2005 16:18:01 +0100, Keith Edmunds wrote
> Noah wrote:
> > this is syntax for running a remote command, right? that is _not_ what I am
> > attempting to do. I want to initiate the rdiff-backup command on the server
> > that is getting backed up.
>
> Noah, this is NOT the syntax fo
On Thu, 18 Aug 2005, Noah wrote:
> okay I got everything configured correctly - well almost everything.
>
> i am finding that ownership on the backup rdiff sevrer is wrong - called
> backup-host below.
>
> look at this.
> "-r-xr-xr-x 1 backup backup 3833936 Apr 16 17:19 kernel"
>
> in fact a
> "Noah" <[EMAIL PROTECTED]>
> wrote the following on Thu, 18 Aug 2005 12:22:19 -0800
> in fact all the files and directories are owned by backup:backup
This is further evidence that the "Unable to change ownership" warning
should be removed---it apparently doesn't clear up confusion :)
