Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid double reporting of files #66

Open
simsong opened this issue Dec 7, 2012 · 0 comments
Open

Avoid double reporting of files #66

simsong opened this issue Dec 7, 2012 · 0 comments

Comments

@simsong
Copy link
Collaborator

simsong commented Dec 7, 2012

Converted from SourceForge issue 2960381, submitted by jessekornblum

Hashdeep currently double reports changed files during an audit. If a file has changed, the program reports both "No match" for the new file and "Known file not used". For example:

$ ~/research/md5deep/hashdeep/hashdeep -vvak known -r tmp
/users/jessek/tmp/tmp/bar: No match
/users/jessek/tmp/tmp/bar: Known file not used

This should instead be reported as the file has changed. A 'new file found' should be reserved for a case when there was no file specified at the given path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant