From: Klaus W. <Kla...@gm...> - 2006-12-06 10:38:48
|
Hello, I am using the rsync transport and playing bit with the new configuration=20 editor in the last beta version of BackupPC. In the documentation you write for $Conf{BackupFilesExclude} =3D undef; "If a hash is used, a special key ``*'' means it applies to all shares." I think this behavior is not working correctly or I interpreted it wrong. I= =20 have several shares in my configuration. In $Conf{BackupFilesExclude} I hav= e=20 one key with * and another key for a share with addition excludes for just= =20 that share. When I take a look in the XferLog then the excludes from "*" ar= e=20 not applied to the share that has specified additional excludes. Is it a bug or not meant to work in that way? Thank you very much! =2D-=20 take care! xo,klaus |
From: Craig B. <cba...@us...> - 2006-12-11 22:59:56
|
Klaus writes: > I am using the rsync transport and playing bit with the new configurati= on=20 > editor in the last beta version of BackupPC. >=20 > In the documentation you write for $Conf{BackupFilesExclude} =3D undef;= > "If a hash is used, a special key ``*'' means it applies to all shares.= " >=20 > I think this behavior is not working correctly or I interpreted it wron= g. I=20 > have several shares in my configuration. In $Conf{BackupFilesExclude} I= have=20 > one key with * and another key for a share with addition excludes for j= ust=20 > that share. When I take a look in the XferLog then the excludes from "*= " are=20 > not applied to the share that has specified additional excludes. >=20 > Is it a bug or not meant to work in that way? Thank you very much! The documentation is ambiguous. "*" is the default for all shares, unless overridden by a specific entry for that share. They are not both used. I changed the documentation to say: If a hash is used, a special key "*" means it applies to all shares that don't have a specific entry. Craig |