codex-admin/autopsy
1
0
Fork 0
mirror of https://github.com/elisspace/autopsy.git synced 2026-09-05 18:14:30 +00:00
Code Issues Releases Wiki Activity

Merge pull request #2063 from eugene7646/pasco

Browse Source 
Treating Pasco output parsing error as warning
This commit is contained in:
Richard Cordovano
2016-04-12 12:00:50 -04:00
parent d241e0882b 908a6b640e
commit 263be3ee0c
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
RecentActivity/src/org/sleuthkit/autopsy/recentactivity/ExtractIE.java
View File

@@ -377,6 +377,14 @@ class ExtractIE extends Extract {
ProcessBuilder processBuilder = new ProcessBuilder(commandLine);
processBuilder.redirectOutput(new File(outputFileFullPath));
processBuilder.redirectError(new File(errFileFullPath));
/*
NOTE on Pasco return codes: There is no documentation for Pasco.
Looking at the Pasco source code I see that when something goes wrong Pasco
returns a negative number as a return code. However, we should still
attempt to parse the Pasco output even if that happens. I have seen
many situations where Pasco output file contains a lot of useful data
and only the last entry is corrupted.
*/
ExecUtil.execute(processBuilder, new DataSourceIngestModuleProcessTerminator(context));
// @@@ Investigate use of history versus cache as type.
} catch (IOException ex) {
@@ -483,7 +491,7 @@ class ExtractIE extends Extract {
this.addErrorMessage(
NbBundle.getMessage(this.getClass(), "ExtractIE.parsePascoOutput.errMsg.errParsingEntry",
this.getName()));
logger.log(Level.SEVERE, "Error parsing Pasco results.", e); //NON-NLS
logger.log(Level.WARNING, "Error parsing Pasco results.", e); //NON-NLS
}
}