From: Les M. <les...@gm...> - 2013-10-31 19:57:45
|
On Thu, Oct 31, 2013 at 2:20 PM, Holger Parplies <wb...@pa...> 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 les...@gm... |