Open VRehnberg opened 1 week ago
Ah, probably misunderstood what -q
does. Probably exits on first match and that's why it is so much faster.
Would still be nice with some possibility to just check for file system errors without dealing with lots of output.
I'd like to use
fd
for checking for presence of stale file handles. Currently I can do:to get a command with a non-zero exit code in presence of such file system errors. However, having to output all the paths makes this much slower than running quietly.
Ideally one or more of the following alternatives should work.
1 Output errors even when rest is silenced
--show-errors -q
2 When there are file system errors output a non-zero exit code
3 Option to give non-zero exit code in presence of file system errors
would either exit with non-zero exit code on first file system error or after everything if there was any file system error.