-
Notifications
You must be signed in to change notification settings - Fork 138
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
ack can get blocked by files #549
Comments
What does grep do in such a situation? |
Grep does wait too. |
If grep has the same problem, then I don't know that ack will be able to do any better. |
If I'm not wrong telling the file position should always fail on such files without blocking. This could be used as a way to detect such files. |
Just a little notice: I have now also opened a ticket for this for grep on Launchpad: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1447216 |
Related: #214 #481 |
I don't think this needs to be fixed at all because it is no bug but just how Linux works. Grepping through whole |
/proc was just an example but such files can appear at any location (for example the text editor SciTE is storing such a file in /tmp if opened). |
Thanks for the input. I'm closing this as acceptable. |
Initially this issue was reported here: https://bugs.launchpad.net/ubuntu/+source/ack-grep/+bug/1267948
It is still reproducible with ack 2.14 and I'm assuming that it just hit a file that waits for input. Maybe ack should check for such files and then skip them.
The text was updated successfully, but these errors were encountered: