Tino writes:
> The excludes are specified per share. So it should read:
> $Conf{BackupFilesExclude} = {
> '/' => [ '/sys/', '/vz/root/', ... ]
> };
>
> ('/' being your share name here if you use rsync via ssh.)
Yes, you're right.
Also, James, in 3.x the excludes are not passed in the
command-
Jeffrey " writes:
> For the part of my routines BackupPC_fixLinks and BackupPC_deleteFile
> that actually try to make new links (or delete old ones), I would like
> to make sure that nothing else is creating or deleting links to the
> pool to avoid collisions.
>
> Specifically, I would like to be
Jeffrey,
Sorry about the delay in replying. I've been really busy lately.
> > 1. If a directory is *empty*, is there any reason for it to have an
> >attrib file?
> >
> >Because in playing around with creating and deleting directory
> contents, I
> >found that sometimes even aft
(BTW: Please start a new thread, don't just reply to another mail.)
On Mon, Dec 01, 2008 at 09:59:35AM -0700, James Ward wrote:
> I've recently built a new BackupPC server with Debian lenny and
> BackupPC version 3.1.0. All my prior BackupPC experience has been
> with 2.*. The strange prob
Hi,
I've recently built a new BackupPC server with Debian lenny and
BackupPC version 3.1.0. All my prior BackupPC experience has been
with 2.*. The strange problem I am having is that my excludes don't
seem to be passed.
Here's the relevant section from the main config:
$Conf{BackupFi
