If the whole share is empty, that is considered indistinguishable from a
general failure. You can control that with
$Conf{BackupZeroFilesIsFatal}. Check the docs for more details.
JH
Brendan Simon wrote:
> I'm getting a fatal error when backing up an empty directory.
> BackupPC server is runn
I'm getting a fatal error when backing up an empty directory.
BackupPC server is running Debian Sarge (backuppc 2.1.1-2sarge2)
Server being backed up is running Debian Etch (rsync 2.6.9-2)
Surely it must be legitimate to backup up an empty directory. Is this a
bogus error message or maybe rsync
Hi,
James Ward wrote on 01.03.2007 at 14:35:50 [[BackupPC-users] Unexpected instant
exit?]:
> [...]
> sudo /var/backups/rsyncSend --server --sender --numeric-ids --perms --
> owner --group --devices --links --times --block-size=2048 --recursive
> --exclude=/proc --exclude=/sys --exclude=/var/l
Actually, the new clients are debian etch! That explains the rsync version
difference.
On Thu, Mar 01, 2007 at 02:35:50PM -0700, James Ward wrote:
> I'm backing up over 200 hosts to three big BackupPC servers. I added
> 5 new clients today and all five are exhibiting the same strange exit
>
I'm backing up over 200 hosts to three big BackupPC servers. I added
5 new clients today and all five are exhibiting the same strange exit
with no discernable errors.
All machines concerned are running debian sarge and BackupPC is
2.1.1. The config file shared for the five boxes:
$Conf{Ba
Bingo! That was it. I set the permissions of SELinux to "permissive" and
everything worked hunky dory.
Setting up rsyncd on the Windows machine has been a bit of a challenge, but it
seems to be working now. Here's the rsyncd.conf file that I'm using:
use chroot = false
strict modes = false
h
Selon Holger Parplies <[EMAIL PROTECTED]>:
> Hi,
>
> Ludovic Gele wrote on 28.02.2007 at 11:04:07 [[BackupPC-users] Data
> Directory]:
> > I've install backuppcpc on debian stable, and I would like to change the
> data
> > directory location. I've try dpkg-reconfigure backuppc, and read the
> > /
OverlordQ wrote:
> The Unicode versions of several functions permit a maximum path length
> of approximately 32,000 characters composed of components up to 255
> characters in length. To specify that kind of path, use the "\\?\" prefix.
>
> http://msdn2.microsoft.com/en-us/library/aa365247.aspx
>
>
Jason Hughes wrote:
> All versions of Windows have a limit of 250-ish characters maximum for a
> full path, including the filename and extension, regardless of file
> system. I'm not aware of a lower limit imposed by the file system or
> OS, but it's likely related. Are you running Unicode-16
