-
Notifications
You must be signed in to change notification settings - Fork 80
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
NSFS endpoint should set its process/threads name in the OS to be identified accurately #8049
Labels
Milestone
Comments
@eshelmarc Should I set the process title (setproctitle) ? this is the property you will get? |
2 tasks
2 tasks
re-opening based on @eshelmarc check, setting the process/thread title seems to be not enough, calling gpfs_ganesha() might do the trick. |
if we don't enable Ganesha in the CES env, does the code path can be reached ? |
we don't need to enable Ganesha to use this interface |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
We want GPFS to identify the noobaa endpoint processes so that it can assist with #8039.
Describe the solution you'd like
Use one of https://linux.die.net/man/2/prctl or pthread_setname_np or setprocname or setproctitle (need to figure out which one) in order to set the process name to "noobaa".
Describe alternatives you've considered
We considered adding a special libgpfs library call that will set the calling process attributes, but setting the name is less coupled.
The text was updated successfully, but these errors were encountered: