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

CA-403620: Drop the usage of fuser in stunnel client proxy #6197

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

minglumlu
Copy link
Member

Two changes in the PR:
Drop the usage of fuser in stunnel client proxy
The drawback of fuser is that it gets too many things involved. E.g. it
is observed that it got stuck on cifs kernel module.

This change uses a cleaner way to remember the stunnel client proxy.
Even when the xapi restarted unexpectedly, it can stop the remnant
stunnel proxy and start a new one.

Make the stunnel proxy local port configurable
Making it configurable can avoid the situation when the port conflicts
with others, e.g. an external program from users.

The drawback of fuser is that it gets too many things involved. E.g. it
is observed that it got stuck on cifs kernel module.

This change uses a cleaner way to remember the stunnel client proxy.
Even when the xapi restarted unexpectedly, it can stop the remnant
stunnel proxy and start a new one.

Signed-off-by: Ming Lu <[email protected]>
Making it configurable can avoid the situation when the port conflicts
with others, e.g. an external program from users.

Signed-off-by: Ming Lu <[email protected]>
@psafont
Copy link
Member

psafont commented Dec 27, 2024

Why isn't the function that uses fuser dropped? (with_client_proxy)

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

Successfully merging this pull request may close these issues.

2 participants