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

filelock generate too many open files #61

Open
Felixxxlz opened this issue Jun 13, 2019 · 1 comment
Open

filelock generate too many open files #61

Felixxxlz opened this issue Jun 13, 2019 · 1 comment

Comments

@Felixxxlz
Copy link

I have to refresh iptable frequently, on suse11 which iptables version is iptables v1.4.16.

It will open filelock /var/run/xtables.lock each time when I do the update, but the filelock wasn't really closed, after a few days it shows too many files open and failed. How could I close these filelocks?

@yannh
Copy link
Contributor

yannh commented Jul 14, 2019

Hi @Felixxxlz , it seems that because you use a version of iptables <1.4.20 that does not support locking, you are failing over to an emulated filelock in go-iptables: e785537#diff-090f71c532949e591510a0220651f3e5

I have proposed a patch that might help, but I think there might need some more work as discussed here #64 - I can eventually propose a patch if the behaviour I'm proposing gets the thumbs up by a maintainer 👍

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