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

Permission check for results.txt should be made at start of the run #128

Open
thulle opened this issue Jan 24, 2023 · 1 comment
Open

Permission check for results.txt should be made at start of the run #128

thulle opened this issue Jan 24, 2023 · 1 comment

Comments

@thulle
Copy link

thulle commented Jan 24, 2023

After churning through 36TB of data I'm met with:

Totally, 3 TiB can be reduced.
Now making results file results.txt
could not open file "results.txt"

While my user has permission to read and write all the checked files, I did not have permission to write in the topmost folder.. moving the check to the start of the run would probably save other idiots a few hours :D

@bordenc
Copy link

bordenc commented Mar 25, 2023

In keeping with the Unix Philosophy, perhaps rdfind should print to standard output by default. The output can either be piped to another program and/or a file. Obviously, leave the -outputname option to save to a file. I understand that accidentally printing GB of results.txt to standard output is unproductive, but at least someone would discover the mistake in their command when their console starts filling up rather than at the end of a multi-hour scan.

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

2 participants