Kenneth L. Owen wrote:
> On this path, my next step is to set up ssh-keys for BackupPC.
> Remember, that I am a novice in Linux. I have instructions for creating
> the keys but find a discrepancy between the instructions (written for
> Debian) and the Fedora setup. When creating keys on the arch
On 10/10 11:54 , Sebastien Sans wrote:
> The compression system of the pool in BackupPc is great, it save a lot
> of place, but I didn't found how to compress the tranfers in order to
> save my bandwidth.
Use compression in your ssh transport.
Here's an example I typically use:
$Conf{RsyncClientC
Carl Wilhelm Soderstrom schrieb:
> On 10/10 11:54 , Sebastien Sans wrote:
>> The compression system of the pool in BackupPc is great, it save a lot
>> of place, but I didn't found how to compress the tranfers in order to
>> save my bandwidth.
>
> Use compression in your ssh transport.
> Here's an
On 10/13 02:56 , Tomasz Chmielewski wrote:
> > $Conf{RsyncClientCmd} = '$sshPath -C -o CompressionLevel=9 -c blowfish-cbc
> > -q -x -l rsyncbakup $host $rsyncPath $argList+';
>
> Unless you're using an obsoleted SSH protocol in version 1, setting
> CompressionLevel does not make any sense - SSH
Adam Goryachev wrote:
>> [EMAIL PROTECTED] ~]# su backuppc
>> bash-3.2$<== This doesn't look as expected
>
> Actually, yes, this is the default prompt, which is usually modified
> in
> your ~/.bashrc or ~/.bash_profile files, but the backuppc user doesn't
> have/use these files
Stephen Vaughan wrote:
> Why use Fedora at all?? Debian is your friend
If you're used to the Fedora way (a.k.a. Red Hat way) of things and
want a distribution with a long lifecycle then I'd say CentOS (or RHEL
if you need paid support) is a better choice than Debian. Debian is a
fine distri
Hi,
Running Backuppc 2.1.2 on a debian linux server and backing up a linux
machine, I ran into a problem backing up a file where the entire path
length was 318 characters. Once I shrunk the path length it worked
perfectly. Has this been fixed in version 3.1? If not, could you add
this to th
Hi,
> Why use Fedora at all?? Debian is your friend
So are so many other Linux distributions... one of the best things about Linux
is the range available.
I personally use Scientific Linux on all my servers (and clients servers) and
have been for many years. If it's good enough for the Large Hed
On Sat, 2008-10-11 at 13:10 +0200, Nils Breunese (Lemonbit) wrote:
> Kenneth L. Owen wrote:
>
> > For a number of years I have run a small home network of windows
> > machines. I recently decided to move my computing to Linux. I now
> > have two machines running Fedora 8. The first machine
With the feedback and help with command line, I was able to create the rsa
keys (Thanks Nils). When I finished creating the keys, I ran the test given
in the instructions:
[EMAIL PROTECTED] .ssh]# su -s /bin/bash - backuppc
-bash-3.2$ chmod -R go-rwx ~/.ssh
-bash-3.2$ ssh -l root 192.168.1.101 w
Maybe I did not make the path clear. I am moving away from Windows. I
already have a system to maintain the Windows system and am trying to set up
a means to have disaster recovery as I transition to Linux. I will only be
archiving files from Linux boxes. -- ken
-Original Message-
From
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth L. Owen wrote:
> With the feedback and help with command line, I was able to create the rsa
> keys (Thanks Nils). When I finished creating the keys, I ran the test given
> in the instructions:
>
> [EMAIL PROTECTED] .ssh]# su -s /bin/bash - ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth L. Owen wrote:
> With the feedback and help with command line, I was able to create the rsa
> keys (Thanks Nils). When I finished creating the keys, I ran the test given
> in the instructions:
>
> [EMAIL PROTECTED] .ssh]# su -s /bin/bash - ba
If I understand you correctly:
[EMAIL PROTECTED] ~]$ su -
Password:
[EMAIL PROTECTED] ~]# su -s /bin/bash - backuppc
-bash-3.2$ ssh -l root WinServer whoami
root
-bash-3.2$
It works this way, too. -- ken
(note: names have been changed to protect confidentiality.)
-Original Message-
F
How difficult would it be to have BackupPC create a link to the last
Full backup. The reason this would be handy to me is I'm required to
backup to tape to a system I don't have much control over. I just want
to tell the backup service a simple directorie to grab. I would like to
be able to tell th
On Mon, 2008-10-13 at 20:01 -0400, Kenneth L. Owen wrote:
> If I understand you correctly:
>
> [EMAIL PROTECTED] ~]$ su -
> Password:
> [EMAIL PROTECTED] ~]# su -s /bin/bash - backuppc
> -bash-3.2$ ssh -l root WinServer whoami
> root
> -bash-3.2$
>
> It works this way, too. -- ken
>
> (note:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yazz D. Atlas wrote:
> How difficult would it be to have BackupPC create a link to the last
> Full backup. The reason this would be handy to me is I'm required to
> backup to tape to a system I don't have much control over. I just want
> to tell the ba
Mr. Yates,
Since Fedora 8 had BackupPC included in the distribution, user backuppc was
already in existence and set for no logon. As root the su -s line changes
the user to 'backuppc'. The test below is run as backuppc user on the
archive machine establishing a connection to the client machine an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth L. Owen wrote:
> Mr. Yates,
> Since Fedora 8 had BackupPC included in the distribution, user backuppc was
> already in existence and set for no logon. As root the su -s line changes
> the user to 'backuppc'. The test below is run as backuppc
Sorry, I missed the command line in the first message. The client machine
name is mixed case of the form 'HOSTname'. I believe that I read in the
documentation that it should be all lower case. I know it works in lower
case when logging in via ssh. The shares that I want to backup are in all
CA
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth L. Owen wrote:
> Sorry, I missed the command line in the first message. The client machine
> name is mixed case of the form 'HOSTname'. I believe that I read in the
> documentation that it should be all lower case. I know it works in lower
>
21 matches
Mail list logo
