On Thu, Oct 31, 2013 at 2:20 PM, Holger Parplies <wb...@parplies.de> wrote:
>>
> That doesn't explain your situation, but it still might be something to think
> about (and we might be seeing one problem on top of and as result of another).
> I agree with Jeffrey - an "Unable to read ..." error *without* a preceeding
> "Can't write len=... to .../RStmp" sounds like a mismatch between file length
> according to attrib file and result of decompression of compressed file -
> probably caused by corruption of the compressed file (or the attrib file,
> though unlikely, because the size is not "way off").
I think that segfault in a perl process needs to be tracked down
before expecting anything else to make sense. Either bad RAM or
mismatching perl libs could break about anything else.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
