Tomasz Chmielewski schrieb:

(...)

> 2. rsync server started on Windows can't open files which long path 
> names (over 260 characters)[1].

(...)

> 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]).

(...)

> 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?
> 
> 
> 
> 3. rsync server started on Windows can't read files with certain 
> characters (Asian etc.).
> 
> This can be addressed by a special cygwin1.dll version available on 
> http://www.okisoft.co.jp/esc/utf8-cygwin/
> 
> A snapshot version of cygwin1.dll would still have to be patched with 
> this UTF-8 patch to solve these three problems.

Actually, no patching is needed.

It is enough to start the rsync service with correct options (and 
probably, use a snapshot version of dygwin1.dll and a recent rsync 
version) - this one line in service.bat should do:

cygrunsrv.exe -I rsyncd -e "CYGWIN=nontsec codepage:utf8" -e 
LC_CTYPE=C-UTF-8 -p /cygdrive/c/rsyncd/rsync.exe -a 
"--config=/cygdrive/c/rsyncd/rsyncd.conf --daemon --no-detach"


So the only problem remaining are these long paths... For this, however, 
PerlRsync needs to be updated.


-- 
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
[email protected]
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-devel
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

Reply via email to