I think the problem is that your rsync module name doesn't match the
> mountpoint. I don't know if that is even possible for '/'. But the
> error message still does not make sense to me.
>
>
I can not use / as rsyncd module name. So I must use something else.
I would like to emphasize that usin
On Mon, Jun 18, 2012 at 6:40 PM, Steve Kieu wrote:
>
> Directory name (rootfs) is generated by backuppc - It think It is based on
> the rsynd module name (if I named it differently then the foldername is
> changed as well).
>
> When doing restore and select download as Tar archive, all is fine, t
> III days, but really, what else does your CPU have to do during the
> backup time? You are mostly disk bound anyway - unless maybe you are
> using IDE or USB drives that need CPU for the I/O work.
>
>
We have a server (nagios) that constantly having load around 15 to 20 -
only two cores. Before
On Mon, Jun 18, 2012 at 7:50 PM, Shawn Carroll wrote:
>
>> Because I do not want to spend cpu time on ssh - And why not rsyncd
>> for local LAN. It should be done that way when encryption is not
>> needed.
>
> Does anyone choose to deal with this by simply specifying no encryption as an
> ssh opt
> Does anyone choose to deal with this by simply specifying no encryption as
> an ssh option?
>
I have heard that ssh no longer support option cipher=none but I will
recheck - last time I did not work for me
>
> Shawn
>
>
> --
> > When the target is a linux system, why not just use rsync over ssh?
>
>
>
>
> Because I do not want to spend cpu time on ssh - And why not rsyncd
> for local LAN. It should be done that way when encryption is not
> needed.
Does anyone choose to deal with this by simply specifying no encry
> under frootfs folder.
>
> When the target is a linux system, why not just use rsync over ssh?
>
>
Because I do not want to spend cpu time on ssh - And why not rsyncd for
local LAN. It should be done that way when encryption is not needed.
Backuppc hardlinks all identical files for its own s
