JohnY wrote:
> On Thu, Jun 12, 2008 at 6:30 PM, Mark Best <markbest AT co.nezperce.id DOT 
> us> wrote:
>> Based upon the limited information - likely you are running a backup job
>> while that file is in use by another process.
>> In case you didn't already know/suspect, files that are open can not be
>> backed up unless you make a 'shadow copy' of it first.
> 
> I agree that's the problem that causes the error log entry.  However,
> my question is regarding the filename inj the entry that's in use.
> 
> As I originially posted, the file name in the error message is:
> 
> "c/WINDOWS/system32/c:/Windows/system32/config/system.LOG"
> 
> which is a non-existent and invalid file name.  I think the correct name is:
> 
> "c:/Windows/system32/config/system.LOG"
> 
> So where is the invalid filename coming from and why is it incorrect?
> I want an accurate error message.

It is coming from rsync(d).  I'm not sure why the name looks like that 
but it might be a hint that the windows version is built with the Cygwin 
.dll that maps windows drive letters into a tree rooted at /cygdrive, so 
starting with c/something could be normal.  What path did you give to 
rsyncd?

-- 
   Les Mikesell
    lesmikesell AT gmail DOT com


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/