Tomasz Chmielewski schrieb: (...)
> The above two problems can be solved: a recent snapshot of > cygwin1.dll[2] can open both files with problematic DLLs and long > filenames, when used with a recent version of rsync (cwRsync[3]). > > I can verify that it really works by starting rsync manually against a > remote rsync server - all files with problematic ACLs and long file > paths are copied: > > > $ rsync -av rsync://[EMAIL PROTECTED]/module localdir > > > However, when I start it from BackupPC, it still bails out on long path > names: > > $ BackupPC_dump -v -f remotehost > (...) > Remote[2]: cannot send long-named file ... > > > Why is that? What limitation is there in BackupPC that it still can't > open long paths? All right, when I use rsync manually and set protocol 28 (default used by BackupPC / RsyncP perl module), it will also fail: rsync --protocol=28 -av "rsync://[EMAIL PROTECTED]/module localdir So I guess PerlRsync needs an update to support protocol 30... -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ BackupPC-devel mailing list BackupPC-devel@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-devel Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
