Hi,

I remember checking the code for the error message

> > > > 2011-03-18   13:15:00 unexpected empty share  name skipped

because I was going to suggest this might be the problem. I was under the
impression that this message is generated for a bogus empty share name entry
as in ...

> $Conf{SmbShareName} = [
>   'share',
>   ''
> ];

... but that this is a warning only and should *not* lead to an aborted
backup. Specifically, the code that reports this condition then skips this
entry. The result should be the same as if it were not there at all (except,
obviously, for the warning message). So I decided to investigate further
before posting, which I obviously didn't get around to :-|.

I might be mistaken, but my guess is that your aborted backup is unrelated to
this issue. Did you consistently get the 'aborted backup' until you removed
the bogus entry, at which point it stopped? Or did you only observe the
'aborted backup' the one time?

Regards,
Holger

------------------------------------------------------------------------------
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and publish 
your website. http://p.sf.net/sfu/ms-webmatrix-sf
_______________________________________________
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/