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

Manually add setuid-bit for executables #80

Open
JanGaertner opened this issue Jul 20, 2021 · 4 comments
Open

Manually add setuid-bit for executables #80

JanGaertner opened this issue Jul 20, 2021 · 4 comments

Comments

@JanGaertner
Copy link

Using Version: 1.3.5

Hello,

after I have installed the hpc-workspace and created a ws user and group I confirmed that ws-db is in fact owned by the ws user and has the ws group. I can also create workspaces as root but when I switch to a normal user I cannot execute ws_allocate

The error message I get is:
"Error: can not change uid." of Line 906 in src/ws.cpp.
From the issue #58 I know that the permissions should have the setuid-bit set. But they do not. Only once I set this manually i can use non root users to allocate some workspace.

It seems to me that this is not the default behavior. What have I done wrong or how should it be done?

@holgerBerger
Copy link
Owner

all as expected, you just missed the part in the HOWTO to set the setuid by hand.

@JanGaertner
Copy link
Author

Could you point to where it is stated in the Admin Guide (https://github.com/holgerBerger/hpc-workspace/blob/master/admin-guide.md)? I cannot find that information

@JanGaertner
Copy link
Author

JanGaertner commented Jul 21, 2021

I do not want to say that it is not there, but that maybe this information could be made more visible.

Is the install command from cmake tested? As an idea, to include the cmake --build . --target install command in the how to?

@holgerBerger
Copy link
Owner

no you are completely right, it was only in the HOWTO file, not in the admin guide.
I added a sentence.

I do not test any automatic install, but it might be there by contributions, I am not 100% sure.

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