One of the more challenging aspects of this is the number of inodes that
BackupPC consumes
is directly related to how many inodes you're backing up. If I recall
correctly, in
BackupPC 4.x, each 'filled' backup will use 2 inodes per object backed up in
addition to
the inode consumed by the uniq
On 3/8/2018 6:59 PM, f...@igh.de wrote:
Craig,
again I return to my issue "No space left on device".
Meanwhile I found the reason: the partition ran out of inodes. As you
wrote under "How much disk space do I need?" one has to have "plenty
of inodes". But what does that mean?
May I ask the fol
Craig,
again I return to my issue "No space left on device".
Meanwhile I found the reason: the partition ran out of inodes. As you
wrote under "How much disk space do I need?" one has to have "plenty
of inodes". But what does that mean?
May I ask the following:
- in the "General Server Inform
You can work around this using something like this:
rsync .ssh/id_rsa.pub root@10.16.0.16:/root
ssh root@10.16.0.16
cat id_rsa.pub >> .ssh/authorized_keys
rm id_rsa.pub
exit
Robert Trevellyan
On Thu, Mar 8, 2018 at 6:05 AM, Marc Gilliatt wrote:
> So I've tried to copy my RSA key to one of my h
So I've tried to copy my RSA key to one of my hosts whilst I was root, and that
worked fine, I could successfully ssh into that host. However, when I switch
users to backuppc, and try to copy the RS key to that same host, I still get
the same error as stated in my previous email.
/usr/bin/ssh-
