Les Mikesell writes: > On Wed, 2006-06-07 at 02:18, Craig Barratt wrote: > > Ralf Gross writes: > > > > > I was looking at the backuppc home page and the sourceforge project page > > > for the bug tracker that is backuppc is using. I couldn't find any info on > > > how to file a bug, what is the recommended way to do this? > > > > BackupPC doesn't use the SF bug tracker. Just post to the devel > > or user mail list. > > > > Several people have seen the "empty output" problem. I haven't > > been able to recreate it. > > Is this related to the issue with rsync 2.6.7 where you have > to replace --devices with -D to fix a change in the way > sockets and other special files are handled as discussed in > a different thread? Maybe you don't have the file types that > trigger it.
Interesting suggestion - these two issues could be related, and it might manifest itself differently depending upon the rsync version. I've sent a newer version of File::RsyncP (a pretty significant rewrite) to a couple of people to see if it behaves the same. Since I should be able to recreate the --devices bug, I can check the same file types against earlier rsync versions. Craig _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
