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
lsof +fg doesn't recognize O_CLOEXEC in file flags on Linux #38
Comments
|
This shows the change in behavior with this patch versus vanilla lsof: I assume (and hope) this fix is valid and correct. |
|
I forget to write "Thank you." |
|
I have some patches about open flags at lsof-org/lsof-linux repo. I will merge them. |
|
I didn't realize there was a separate lsof-linux project. That's why I didn't find the modifications - I did search this repo of course. (I was confused by the move to github, which pointed to https://github.com/lsof-org/lsof.) I'm the one to say thank you. Looking forward to those patches. Feel free to close this ticket if it is considered invalid. |
|
I'm pulling changes in lsof-linux repo to this lsof repo now. |
|
Close via #40. |
lsof +fg doesn't recognize O_CLOEXEC in file flags on Linux. It displays this flag as "0x80000". It should probably be displayed as "CX".
This was pointed out in this RedHat bugzilla issue.
I assume Linux's O_CLOEXEC is identical to other platforms' POF_CLOEXEC. I took a stab at this. Will post a PR.
The text was updated successfully, but these errors were encountered: