On Mon, 28 Oct 2013 10:39:44 -0400 "Thomas H. George" <m...@tomgeorge.info> wrote:
Thomas> I tried adding --exclude-sockets to the command line but it had Thomas> no effect, the backup again failed with the same Thomas> SpecialFileError as above. Joe> My guess is that the first time this socket was backed up, it Joe> succeeded (i.e., the backup path wasn't too long). But the next Joe> time it was backed up, the path became too long because the Joe> snapshot file had "rdiff-backup-data/increments/" added to the path Joe> at the beginning, and it had something like Joe> ".2009-06-12T19:35:55-04:00.snapshot" added at the end of the file Joe> name. Joe> Once it became part of your backup, there is no easy way of getting Joe> around it trying to create a snapshot file when the next backup Joe> runs. Using "--exclude-sockets" is effectively the same as saying Joe> the file no longer exists (which is equivalent to deleting the Joe> file). When the next backup runs, rdiff-backup will try to create Joe> a snapshot of the deleted (or excluded) file, and that will Joe> continue to fail because the full path name of the snapshot has Joe> grown too long. And now I get it too 8-o Off to build my own version of the package with Joe's patch. -- Please *no* private copies of mailing list or newsgroup messages. gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD Funny pic: http://bit.ly/ZNE2MX _______________________________________________ rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
